From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2] CRL updater: Update script for OpenVPNs CRL
Date: Tue, 13 Feb 2018 07:02:57 +0100 [thread overview]
Message-ID: <1518501777.5749.8.camel@ipfire.org> (raw)
In-Reply-To: <1518387911.2498.18.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
Hi Michael,
thanks for merging.
Am Sonntag, den 11.02.2018, 22:25 +0000 schrieb Michael Tremer:
> Hello,
>
> I merged this patch into the openssl-11 branch and rebased the
> branch.
>
> What other steps are urgently necessary that we can roll out OpenVPN
> 2.4? Are the CGI changes necessary or new features?
there is the need to make the changes for '--script-security' and to
add '--ncp-disable' in ovpnmain.cgi.
Also the integration of the directives via update.sh for the core
update needs to be made since a server stop|start do not includes the
changes into server.conf.
So there are two steps left for a roll out of a 2.4 minimum version.
Should i send this in two patches or better in one ?
In which core update should this be delivered ?
Greetings,
Erik
next prev parent reply other threads:[~2018-02-13 6:02 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
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 [this message]
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=1518501777.5749.8.camel@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