gitea: fix INSTALL script

With current INSTALL sed process reveals generated secret key; it can be viewed by monitoring /proc or by using extrace.
Also sed pattern <SECRET_KEY> fails, since there no such substring in provided sample configuration.

gitea will change all secrets in configuration file right after web based installation process.
This commit is contained in:
sineemore 2020-02-24 18:18:54 +03:00 committed by Michael Aldridge
parent 9ea1cd03d3
commit 57548c7bd5
2 changed files with 5 additions and 13 deletions

View file

@ -1,13 +1,5 @@
case "$ACTION" in case "${ACTION}" in
post) post)
if [ "$UPDATE" = "yes" ] ; then
:
else
# This sets the secret key which would otherwise be
# distributed as a static packaged value
secret="$(tr -dc '[:alnum:]' < /dev/urandom | head -c32)"
sed -i "s!<SECRET_KEY>!$secret!" etc/gitea.conf
fi
chown _gitea:_gitea etc/gitea.conf chown _gitea:_gitea etc/gitea.conf
;; ;;
esac esac

View file

@ -1,7 +1,7 @@
# Template file for 'gitea' # Template file for 'gitea'
pkgname=gitea pkgname=gitea
version=1.10.6 version=1.10.6
revision=1 revision=2
build_style=go build_style=go
go_import_path=code.gitea.io/gitea go_import_path=code.gitea.io/gitea
# This could be done with build options, but these are built in with the # This could be done with build options, but these are built in with the