From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/2] backup: Update OpenVPN CRL
Date: Fri, 07 Oct 2022 14:50:16 +0000 [thread overview]
Message-ID: <20221007145017.4096212-1-michael.tremer@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
After a backup is restored, the CRL might be out of data and client
won't be able to connect to the server any more.
This will immediately update the CRL should it require an update.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
---
config/backup/backup.pl | 3 +++
1 file changed, 3 insertions(+)
diff --git a/config/backup/backup.pl b/config/backup/backup.pl
index 54957a814..6fd9e45bb 100644
--- a/config/backup/backup.pl
+++ b/config/backup/backup.pl
@@ -184,6 +184,9 @@ restore_backup() {
# move nobeeps if exist
[ -e "/var/ipfire/ppp/nobeeps" ] && mv /var/ipfire/ppp/nobeeps /var/ipfire/red/nobeeps
+ # Update OpenVPN CRL
+ /etc/fcron.daily/openvpn-crl-updater
+
return 0
}
--
2.30.2
next reply other threads:[~2022-10-07 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 14:50 Michael Tremer [this message]
2022-10-07 14:50 ` [PATCH 2/2] openvpnctrl: Update CRL before starting the client daemon Michael Tremer
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=20221007145017.4096212-1-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