From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Introduce Negotiable Crypto Parameters for roadwarriors
Date: Thu, 30 Aug 2018 15:08:36 +0100 [thread overview]
Message-ID: <bf246e18d818252b01deec78b1291ca801a9b65b.camel@ipfire.org> (raw)
In-Reply-To: <e40e1d14ef0fd4a75bb30cea9a85b6847916d1f9.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Thu, 2018-08-30 at 16:02 +0200, ummeegge wrote:
> Hi Michael,
>
> Am Donnerstag, den 30.08.2018, 12:59 +0100 schrieb Michael Tremer:
> > A very long discussion has been had about whether we should continue
> > supporting
> > OpenVPN and the majority of the arguments were against OpenVPN. On
> > paper, it is
> > just too broken; in the wrong hands and there were other reasons like
> > "one VPN
> > implementation is enough for a start", too.
>
> OK haven´t heard about this discussion before but good to know now so i
> will stop further development for OpenVPN.
This has been decided at the developer summit in 2015 at the Mozilla office.
https://wiki.ipfire.org/ids/2015/results
> > > Best,
> > >
> > > Erik
>
>
next prev parent reply other threads:[~2018-08-30 14:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 7:25 Erik Kapfer
2018-08-07 13:10 ` Michael Tremer
2018-08-07 16:19 ` ummeegge
2018-08-08 7:55 ` Michael Tremer
2018-08-08 10:32 ` ummeegge
2018-08-14 11:11 ` ummeegge
2018-08-14 11:21 ` Michael Tremer
2018-08-27 7:20 ` Michael Tremer
2018-08-27 16:21 ` ummeegge
2018-08-28 10:21 ` Michael Tremer
2018-08-28 19:35 ` ummeegge
2018-08-29 10:33 ` Michael Tremer
2018-08-29 21:49 ` ummeegge
2018-08-30 7:35 ` Michael Tremer
2018-08-30 10:31 ` ummeegge
2018-08-30 11:59 ` Michael Tremer
2018-08-30 14:02 ` ummeegge
2018-08-30 14:08 ` Michael Tremer [this message]
2018-09-05 15:22 ` Kienker, Fred
2018-09-09 12:46 ` 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=bf246e18d818252b01deec78b1291ca801a9b65b.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