[taler-sandcastle-ng] branch master updated: permissions

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository sandcastle-ng.

The following commit(s) were added to refs/heads/master by this push:
     new b767886  permissions
b767886 is described below

commit b767886828b82da468f62f0bcc3646345c0d91b9
Author: Florian Dold <florian@dold.me>
AuthorDate: Tue Sep 3 22:51:26 2024 +0200

    permissions
---
 scripts/demo/setup-sandcastle.sh | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/scripts/demo/setup-sandcastle.sh b/scripts/demo/setup-sandcastle.sh
index 5386e29..67ab332 100755
--- a/scripts/demo/setup-sandcastle.sh
+++ b/scripts/demo/setup-sandcastle.sh
@@ -136,6 +136,7 @@ persist_exchange_key /var/lib/taler/exchange-offline 
exchange-offline
 # We need to adjust file ownership, as the container might have different user 
and group
 # IDs than the volume. That can happen when the packages in the container are 
installed
 # in a different order.
+# This is only relevant for non-root ownership.
 
 chown taler-exchange-offline:taler-exchange-offline 
/talerdata_persistent/exchange-offline
 chown --recursive taler-exchange-offline:taler-exchange-offline 
/var/lib/taler/exchange-offline/*
@@ -144,6 +145,9 @@ chown --recursive 
taler-exchange-secmod-cs:taler-exchange-secmod /var/lib/taler/
 chown --recursive taler-exchange-secmod-rsa:taler-exchange-secmod 
/var/lib/taler/exchange-secmod-rsa
 chown --recursive taler-exchange-secmod-eddsa:taler-exchange-secmod 
/var/lib/taler/exchange-secmod-eddsa
 
+chown root:taler-exchange-db /etc/taler/secrets/auditor-db.secret.conf
+chown root:taler-exchange-db /etc/taler/secrets/exchange-db.secret.conf
+
 # FIXME: More permissions to adjust!
 
 # Usage: get_credential_pw COMPONENT/ACCOUNT
@@ -584,6 +588,7 @@ cat <<EOF >/etc/taler/conf.d/auditor.conf
 PUBLIC_KEY = $AUDITOR_PUB
 EOF
 
+
 taler-auditor-dbconfig
 
 systemctl enable --now taler-auditor.target

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.