From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 0ebb271d1ec8b68f73dbd396b0f3a0aa4a50a501
Date: Tue, 13 Jun 2023 15:08:14 +0000 [thread overview]
Message-ID: <4QgX4G4W9rz2xXF@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1761 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 0ebb271d1ec8b68f73dbd396b0f3a0aa4a50a501 (commit)
from d57f305a1042fb69aa597426ee3f62ccce384f80 (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 0ebb271d1ec8b68f73dbd396b0f3a0aa4a50a501
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jun 12 13:55:37 2023 +0000
ovpnmain.cgi: Fix return code of legacy check function
https://lists.ipfire.org/pipermail/development/2023-June/016042.html
Reported-by: Adolf Belka <adolf.belka(a)ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/ovpnmain.cgi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/html/cgi-bin/ovpnmain.cgi b/html/cgi-bin/ovpnmain.cgi
index a210e0509..efc85b77b 100755
--- a/html/cgi-bin/ovpnmain.cgi
+++ b/html/cgi-bin/ovpnmain.cgi
@@ -144,9 +144,9 @@ sub iscertlegacy
my @certinfo = &General::system_output("/usr/bin/openssl", "pkcs12", "-info", "-nodes",
"-in", "$file.p12", "-noout", "-passin", "pass:''");
if (index ($certinfo[0], "MAC: sha1") != -1) {
- return 0;
+ return 1;
}
- return 1;
+ return 0;
}
sub haveOrangeNet
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-06-13 15:08 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=4QgX4G4W9rz2xXF@people01.haj.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