From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 637885839b5a2d6baeffb7fb37967c5b1bf7f84f
Date: Sun, 26 May 2019 16:21:11 +0100 [thread overview]
Message-ID: <20190526152111.7EC2F84FDC4@people01.i.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via 637885839b5a2d6baeffb7fb37967c5b1bf7f84f (commit)
from 8fad3a5941a1a0553bc3cbd0ad577d9067f3dd6b (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 637885839b5a2d6baeffb7fb37967c5b1bf7f84f
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun May 26 16:17:04 2019 +0200
core132: security conf should not executable
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/132/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/132/update.sh b/config/rootfiles/core/132/update.sh
index 979f31925..fa4553625 100644
--- a/config/rootfiles/core/132/update.sh
+++ b/config/rootfiles/core/132/update.sh
@@ -90,7 +90,7 @@ ldconfig
# create main/security file
touch /var/ipfire/main/security
-chmod 755 /var/ipfire/main/security
+chmod 644 /var/ipfire/main/security
chown nobody:nobody /var/ipfire/main/security
# Update Language cache
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2019-05-26 15:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190526152111.7EC2F84FDC4@people01.i.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox