From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] CRL updater: Update script for OpenVPN CRL
Date: Sat, 03 Feb 2018 21:20:32 +0100 [thread overview]
Message-ID: <73B70A3C-9882-4C28-967E-525019450348@ipfire.org> (raw)
In-Reply-To: <F31EA628-6BE2-403B-A2C5-2700896EFDC3@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
Hello Michael,
some thoughts causing two quested points
>>> +# Convert seconds to days
>>> +NEXTUPDATE="$((EXPIRINGDATEINSEC / DAYINSEC))";
>>> +# Update of the CRL in days before CRL expiring date
>>> +UPDATE="2";
>>
>> I think we should update every 14 days if the usual expiry time is 30.
>> Therefore we will never get too close by accident.
>
> So i would need then an frcontab entry and another location for the script since the fcron directories provides only daily, weekly and monthly.
> Another possibility might be a weekly check so we can use the fcron directories ?
In case machines are off while the script performs his weekly check (no 24/7er) the next check will be made one/two week(s) later which might be a long time if you do not know where the problem is.
I would do make there possibly a daily check and would also set the UPDATE to a week or 5 days instead of the current 2 before expiration date so more days can be grabbed even the check should be a fast one.
>> Should we catch any errors of the openssl command?
>
> OK i would then use may a '2>&1 | logger -i -t openvpn' instead so we get an OpenSSL command output in messages if the CRL has been renewed.
Have here two possibilities.
1)
in error case:
Feb 3 17:56:03 ipfire-server crl_updater[18986]: /etc/fcron.daily/ovpn_crl_updater.sh: line 56: /usr/bin/opensl: No such file or directory
if successful:
Feb 3 17:56:41 ipfire-server crl_updater[18998]: Using configuration from /var/ipfire/ovpn/openssl/ovpn.cnf
which equals to the OpenSSL command output ( 2>&1 | logger ).
or 2)
in error case:
Feb 2 19:02:34 ipfire-server openvpn: /etc/fcron.daily/ovpn_crl_updater.sh - CRL update failed
if successful:
Feb 2 19:03:19 ipfire-server openvpn: /etc/fcron.daily/ovpn_crl_updater.sh - CRL has been updated
if else query echo´s a defined message so search string like failed or updated can also be logged ?
Otherwise all other quested changes has been made and are ready so far, might be nice to push the remaining CGI changes soon i think :-) .
Greetings,
Erik
next prev parent reply other threads:[~2018-02-03 20:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 16:38 [PATCH] OpenVPN: Update to version 2.4.4 Erik Kapfer
2018-01-30 20:00 ` Michael Tremer
2018-02-02 6:34 ` [PATCH] CRL updater: Update script for OpenVPN CRL Erik Kapfer
2018-02-02 10:51 ` Michael Tremer
2018-02-02 19:19 ` ummeegge
2018-02-03 20:20 ` ummeegge [this message]
2018-02-06 0:44 ` Michael Tremer
2018-02-06 9:24 ` ummeegge
2018-02-06 16:34 ` Michael Tremer
2018-02-06 20:09 ` [PATCH v2] CRL updater: Update script for OpenVPNs CRL Erik Kapfer
2018-02-06 21:45 ` Michael Tremer
2018-02-07 17:31 ` Erik Kapfer
2018-02-11 22:25 ` Michael Tremer
2018-02-13 6:02 ` ummeegge
2018-02-13 6:07 ` Horace Michael
2018-02-13 10:00 ` ummeegge
2018-02-13 14:21 ` Horace Michael
2018-02-14 14:09 ` ummeegge
2018-02-13 13:13 ` ummeegge
2018-02-14 12:22 ` Michael Tremer
2018-02-14 13:24 ` ummeegge
2018-02-14 20:27 ` Michael Tremer
2018-02-15 6:18 ` ummeegge
2018-02-15 11:05 ` 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=73B70A3C-9882-4C28-967E-525019450348@ipfire.org \
--to=ummeegge@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