From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 4176a1badace1fd2c06c375f9c2d7562edee870a
Date: Wed, 25 Dec 2013 15:13:53 +0100 [thread overview]
Message-ID: <20131225141354.2871C205D5@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1578 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 4176a1badace1fd2c06c375f9c2d7562edee870a (commit)
from 4c7fe35f9edfe8e4626195758fb6774bdc418d04 (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 4176a1badace1fd2c06c375f9c2d7562edee870a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Dec 25 15:12:34 2013 +0100
openvpn: Fix verify script.
Former versions of openvpn called the script where the arguments
in the certificate's common name where separated by /.
Now, those are separated by ", " (comma, space).
-----------------------------------------------------------------------
Summary of changes:
config/ovpn/verify | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/config/ovpn/verify b/config/ovpn/verify
index 44ed110..1a1fcb5 100644
--- a/config/ovpn/verify
+++ b/config/ovpn/verify
@@ -30,8 +30,8 @@ my $CN = $ARGV[1];
exit 0 unless ($DEPTH eq "0");
# Strip the CN from the X509 identifier.
-$CN =~ /\/CN=(.*)$/i;
-$CN = $1;
+$CN =~ /(\/|,\ )CN=(.*)$/i;
+$CN = $2;
my %confighash = ();
if (-f "${General::swroot}/ovpn/ovpnconfig"){
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-12-25 14:13 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=20131225141354.2871C205D5@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