From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Added needed directive for v2.4 update
Date: Thu, 15 Feb 2018 14:43:22 +0100 [thread overview]
Message-ID: <1518702202.4781.1.camel@ipfire.org> (raw)
In-Reply-To: <1518692427.15001.40.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]
Am Donnerstag, den 15.02.2018, 11:00 +0000 schrieb Michael Tremer:
> Hi,
>
> okay, that's fine. I will add this to the update script of that core
> update
> then.
Great thanks. I think we should be then OpenVPN-2.4 ready for the
first...
>
> -Michael
>
> On Thu, 2018-02-15 at 11:56 +0100, ummeegge wrote:
> >
> > Hi Michael,
> >
> >
> > Am Donnerstag, den 15.02.2018, 10:40 +0000 schrieb Michael Tremer:
> > >
> > > Hi,
> > >
> > > this looks good. I will merge this soon.
> > >
> > > How do we convert existing configuration files?
> > i would do it like this:
> >
> > #!/bin/bash
> >
> > # Changed and new OpenVPN-2.4 directives will wrote to server.conf
> > and renew
> > CRL while update an core update
> > if [ -e /var/ipfire/ovpn/server.conf ]; then
> > if pgrep openvpn >/dev/null; then
> > openvpnctrl -k
> > sed -i -e 's/script-security 3 system/script-security
> > 3/' -e
> > '/status .*/ a ncp-disable' /var/ipfire/ovpn/server.conf
> > openssl ca -gencrl -keyfile
> > /var/ipfire/ovpn/ca/cakey.pem -cert
> > /var/ipfire/ovpn/ca/cacert.pem -out /var/ipfire/ovpn/crls/cacrl.pem
> > -config
> > /var/ipfire/ovpn/openssl/ovpn.cnf
> > openvpnctrl -s
> > else
> > sed -i -e 's/script-security 3 system/script-security
> > 3/' -e
> > '/status .*/ a ncp-disable' /var/ipfire/ovpn/server.conf
> > openssl ca -gencrl -keyfile
> > /var/ipfire/ovpn/ca/cakey.pem -cert
> > /var/ipfire/ovpn/ca/cacert.pem -out /var/ipfire/ovpn/crls/cacrl.pem
> > -config
> > /var/ipfire/ovpn/openssl/ovpn.cnf
> > fi
> > fi
> >
> > # EOF
> >
> >
> > which includes also an update of the CRL to stay save also in that
> > manner
> >
> >
> > Best,
> >
> > Erik
prev parent reply other threads:[~2018-02-15 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 4:43 Erik Kapfer
2018-02-15 10:40 ` Michael Tremer
2018-02-15 10:56 ` ummeegge
2018-02-15 11:00 ` Michael Tremer
2018-02-15 13:43 ` 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=1518702202.4781.1.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