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: Re: [PATCH] CRL updater: Update script for OpenVPN CRL
Date: Tue, 06 Feb 2018 16:34:12 +0000	[thread overview]
Message-ID: <1517934852.21272.90.camel@ipfire.org> (raw)
In-Reply-To: <34F195E4-7AE9-4DD9-9C5F-9F0B4E9640E4@ipfire.org>

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

Hi,

On Tue, 2018-02-06 at 10:24 +0100, ummeegge wrote:
> Hello,
> 
> > > 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.
> > 
> > Cron will take care of this. It will automatically perform the cron jobs a
> > little while after the system has been booted and when the cron jobs should
> > have
> > been executed while it was shut down.
> > 
> > https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/cron/crontab;h=4561
> > f4a2
> > 43239b8b5bd3525c067dc6a70395489c;hb=HEAD#l13
> > 
> > It's the "bootrun" argument there.
> 
> Thanks for clarification haven´t had that in mind. Will deliver the updater
> then to 'frcon.weekly'. Will also set the update before expiration interval to
> 10 days before, 8 might be also OK for a weekly cronjob but possibly better to
> have 2 days + ?!

I think daily is better. That makes things more predictable and it does not hurt
to renew every 14 days to never get close to the expiration date.

> 
> > > 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 ). 
> > 
> > Do we need to log the output of OpenSSL? A line that says something like
> > "Could
> > not update the OpenVPN CA CRL" should do, shouldn't it? People should run
> > the
> > script themselves then and see what is going wrong.
> 
> No i don´t think so, lines in messages looks even better then. Did that now
> like you suggested.
> 
> > > 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 :-) .
> > 
> > Cool.
> > 
> > Let me know if I can be of any more help.
> 
> Great thanks for your offer and your help. If there is no veto for the above
> changes i will deliver the patch today in the evening.
> 
> Have also fetched the actual openssl-11 branch with all needed changes, thanks
> for keeping this up to date :-) .
> 
> All the best,
> 
> Erik
> 

-Michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-02-06 16:34 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
2018-02-06  0:44         ` Michael Tremer
2018-02-06  9:24           ` ummeegge
2018-02-06 16:34             ` Michael Tremer [this message]
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=1517934852.21272.90.camel@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