public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. ea6d6642a9520469dd845b52a860017844f7c67b
Date: Thu, 02 Jan 2014 17:38:16 +0100	[thread overview]
Message-ID: <20140102163817.8536E20AEE@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1400 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  ea6d6642a9520469dd845b52a860017844f7c67b (commit)
      from  61719727b43fb4e323da652eaa6619778e70f799 (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 ea6d6642a9520469dd845b52a860017844f7c67b
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Thu Jan 2 17:37:53 2014 +0100

    OpenVPN verify script must be owned by root.

-----------------------------------------------------------------------

Summary of changes:
 lfs/openvpn | 1 +
 1 file changed, 1 insertion(+)

Difference in files:
diff --git a/lfs/openvpn b/lfs/openvpn
index 727d374..053d581 100644
--- a/lfs/openvpn
+++ b/lfs/openvpn
@@ -96,6 +96,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
 	chmod 660 /var/log/ovpnserver.log
 	chmod 700 /var/ipfire/ovpn/certs
 	mv -v /var/ipfire/ovpn/verify /usr/lib/openvpn/verify
+	chown root:root /usr/lib/openvpn/verify
 	chmod 755 /usr/lib/openvpn/verify
 	@rm -rf $(DIR_APP)
 	@$(POSTBUILD)


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2014-01-02 16:38 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=20140102163817.8536E20AEE@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