public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2] OpenVPN: Update to version 2.4.4
Date: Fri, 02 Feb 2018 07:50:48 +0100	[thread overview]
Message-ID: <AD8B1959-209C-4285-BBF4-12AA4FD4FE46@ipfire.org> (raw)
In-Reply-To: <1517484830.21272.19.camel@ipfire.org>

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

Hi Michael,
did a rebase of the branch but it seems that the ROOTFILE changes are not integrated in the CRL updater commit --> https://lists.ipfire.org/pipermail/development/2018-February/003997.html even i have added it to the commit. Can you may integrate the line 

etc/fcron.daily/ovpn_crl_updater.sh

again to the OpenVPN ROOTFILE ?

Thanks and greetings,

Erik


Am 01.02.2018 um 12:33 schrieb Michael Tremer:

> Hi,
> 
> yes I will keep the openssl-11 branch up to date. Make sure that you rebase any
> local branches on it instead of merging it because I might remove commits in
> between.
> 
> I do not know when I am going to merge everything into next. So far at least the
> OpenVPN stuff in the webUI are missing and I haven't really done any testing
> with the new OpenSSL library, yet. I just built it. Therefore I have no idea
> what bugs we might still find.
> 
> Best,
> -Michael


      reply	other threads:[~2018-02-02  6:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1517416911.2586.95.camel@ipfire.org>
2018-02-01  8:35 ` ummeegge
2018-02-01 11:33   ` Michael Tremer
2018-02-02  6:50     ` ummeegge [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=AD8B1959-209C-4285-BBF4-12AA4FD4FE46@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