public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 3/3] openvpn-crl-updater: Update for the changed configuration file
Date: Thu, 18 Apr 2024 21:36:54 +0000	[thread overview]
Message-ID: <20240418213654.3321580-3-michael.tremer@ipfire.org> (raw)
In-Reply-To: <20240418213654.3321580-1-michael.tremer@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]

Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
---
 config/ovpn/openvpn-crl-updater | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/config/ovpn/openvpn-crl-updater b/config/ovpn/openvpn-crl-updater
index 5fbe21080..d22f8f78c 100644
--- a/config/ovpn/openvpn-crl-updater
+++ b/config/ovpn/openvpn-crl-updater
@@ -43,7 +43,9 @@ OVPN="/var/ipfire/ovpn"
 CRL="${OVPN}/crls/cacrl.pem"
 CAKEY="${OVPN}/ca/cakey.pem"
 CACERT="${OVPN}/ca/cacert.pem"
-OPENSSLCONF="${OVPN}/openssl/ovpn.cnf"
+
+# Use an alternative OpenSSL configurtion file
+export OPENSSL_CONF="/usr/share/openvpn/openssl.cnf"
 
 # Check if CRL is presant or if OpenVPN is active
 if [ ! -e "${CAKEY}" ]; then
@@ -76,7 +78,7 @@ UPDATE="14"
 ## Mainpart
 # Check if OpenVPNs CRL needs to be renewed
 if [ ${NEXTUPDATE} -le ${UPDATE} ]; then
-    if openssl ca -gencrl -keyfile "${CAKEY}" -cert "${CACERT}" -out "${CRL}" -config "${OPENSSLCONF}"; then
+    if openssl ca -gencrl -keyfile "${CAKEY}" -cert "${CACERT}" -out "${CRL}"; then
 		logger -t openvpn "CRL has been updated"
     else
 		logger -t openvpn "error: Could not update CRL"
-- 
2.39.2


      parent reply	other threads:[~2024-04-18 21:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 21:36 [PATCH 1/3] ovpnmain.cgi: Define OpenSSL configuration globally Michael Tremer
2024-04-18 21:36 ` [PATCH 2/3] OpenVPN: Move the OpenSSL configuration file out of /var/ipfire Michael Tremer
2024-06-05 11:26   ` Adolf Belka
2024-06-05 11:33     ` Adolf Belka
2024-06-05 11:52       ` Adolf Belka
2024-06-07  8:22         ` Adolf Belka
2024-06-07 16:01           ` [PATCH] " Michael Tremer
2024-06-08  8:40             ` Adolf Belka
2024-06-08 10:14               ` Michael Tremer
2024-06-08 10:43                 ` Adolf Belka
2024-06-08 11:00                   ` Adolf Belka
2024-06-08 11:16                   ` Adolf Belka
2024-06-09  7:58                     ` Adolf Belka
2024-06-10 16:02                       ` Michael Tremer
2024-06-11  9:09                         ` Adolf Belka
2024-06-07 16:03           ` [PATCH 2/3] " Michael Tremer
2024-06-07 16:24             ` Adolf Belka
2024-06-07 19:46               ` Adolf Belka
2024-04-18 21:36 ` Michael Tremer [this message]

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=20240418213654.3321580-3-michael.tremer@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@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