public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Kienker, Fred" <fkienker@at4b.com>
To: development@lists.ipfire.org
Subject: RE: [PATCH] OpenVPN: Introduce Negotiable Crypto Parameters for roadwarriors
Date: Wed, 05 Sep 2018 11:22:18 -0400	[thread overview]
Message-ID: <H000006e0043f07c.1536160938.mail.at4b.net@MHS> (raw)
In-Reply-To: <bf246e18d818252b01deec78b1291ca801a9b65b.camel@ipfire.org>

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

-----Original Message-----
From: Michael Tremer <michael.tremer(a)ipfire.org> 
Sent: 30 August, 2018 10:09
To: ummeegge <ummeegge(a)ipfire.org>; development(a)lists.ipfire.org
Subject: Re: [PATCH] OpenVPN: Introduce Negotiable Crypto Parameters for 
roadwarriors

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
> 
> 

If OpenVPN is going to be dropped, then what will replace it? Is IPsec 
going to be the only supported VPN solution?

Best regards,
Fred Kienker


  reply	other threads:[~2018-09-05 15:22 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
2018-09-05 15:22                               ` Kienker, Fred [this message]
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=H000006e0043f07c.1536160938.mail.at4b.net@MHS \
    --to=fkienker@at4b.com \
    --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