From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 7514fe47f6b2caf5a1dfc80de3a539975b753b21
Date: Fri, 10 Jan 2014 16:00:47 +0100 [thread overview]
Message-ID: <20140110150048.476FF20AEC@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1664 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, fifteen has been updated
via 7514fe47f6b2caf5a1dfc80de3a539975b753b21 (commit)
from 2505d2763efef1c2339f84f8130594c0ee7feaec (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 7514fe47f6b2caf5a1dfc80de3a539975b753b21
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Jan 10 15:59:33 2014 +0100
convert-outgoingfw: Fix permissions of p2protocols configuration file.
World access can not be granted to this file. It must
be writable by nobody and can be read by all users.
-----------------------------------------------------------------------
Summary of changes:
config/firewall/convert-outgoingfw | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/firewall/convert-outgoingfw b/config/firewall/convert-outgoingfw
index d2672cb..4f8bcdc 100755
--- a/config/firewall/convert-outgoingfw
+++ b/config/firewall/convert-outgoingfw
@@ -675,5 +675,5 @@ sub build_ovpn_grp
sub process_p2p
{
copy("/var/ipfire/outgoing/p2protocols","/var/ipfire/firewall/p2protocols");
- chmod oct('0777'), '/var/ipfire/firewall/p2protocols';
+ chown 99, 99, '/var/ipfire/firewall/p2protocols';
}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-01-10 15:00 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=20140110150048.476FF20AEC@argus.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