From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: vtol <vtol@gmx.net>
Cc: wireguard <wireguard@lists.zx2c4.com>
Subject: Re: WG interface to ipv4
Date: Sun, 6 May 2018 03:27:35 +0200 [thread overview]
Message-ID: <CAHmME9o4PUH_+DNMC1cWPcRRfDvdeB0k_6bJMgsMMN8JSq51PA@mail.gmail.com> (raw)
In-Reply-To: <1a630d88-d7f8-7437-89a2-786b3da5888c@gmx.net>
On Sat, May 5, 2018 at 7:53 PM, =D1=BD=D2=89=E1=B6=AC=E1=B8=B3=E2=84=A0 <vt=
ol@gmx.net> wrote:
> I trust that such is available and common practice with other VPN apps.
I should point out that "other VPN apps are doing it" is mostly not a
motivation for adding a nob. We're trying to aim with WireGuard as
close to a nob-less security model as possible. This is indeed a
substantially different goal from other projects, many of which love
to add features and choices. On the other hand, WireGuard aims to look
at the complete system and tries to determine what set of parameters
always provide security in the model we're going for. For example,
most other VPN apps let you choose your "cipher suite". DES? Blowfish?
AES? XTEA? This project has a bit of a different focus. I realize this
might be less exciting to watch, but I do believe this approach will
nudge us a tiny bit closer to having secure software.
next prev parent reply other threads:[~2018-05-06 1:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 16:57 ѽ҉ᶬḳ℠
2018-05-04 1:06 ` Jason A. Donenfeld
2018-05-04 9:27 ` ѽ҉ᶬḳ℠
2018-05-05 3:44 ` Jason A. Donenfeld
2018-05-05 8:18 ` ѽ҉ᶬḳ℠
2018-05-05 9:28 ` Kalin KOZHUHAROV
2018-05-05 17:33 ` Christophe-Marie Duquesne
2018-05-05 17:53 ` ѽ҉ᶬḳ℠
2018-05-06 1:27 ` Jason A. Donenfeld [this message]
2018-05-06 7:31 ` ѽ҉ᶬḳ℠
2018-05-06 9:00 ` Matthias Urlichs
2018-05-06 9:26 ` ѽ҉ᶬḳ℠
2018-05-06 0:14 ` RFE: Name of peer in configuration John Huttley
2018-05-06 1:21 ` WG interface to ipv4 Jason A. Donenfeld
2018-05-06 8:58 ` ѽ҉ᶬḳ℠
2018-05-06 13:34 ` Jordan Glover
2018-05-06 14:12 ` ѽ҉ᶬḳ℠
2018-05-06 14:17 ` Jason A. Donenfeld
2018-05-06 15:21 ` Toke Høiland-Jørgensen
2018-05-06 16:33 ` ѽ҉ᶬḳ℠
2018-05-06 18:09 ` Jordan Glover
2018-05-06 19:39 ` ѽ҉ᶬḳ℠
2018-05-06 21:37 ` Android Configuration File John Huttley
2018-05-06 22:10 ` Jason A. Donenfeld
2018-05-07 4:22 ` John Huttley
2018-05-07 13:35 ` WG interface to ipv4 Christophe-Marie Duquesne
2018-05-07 16:34 ` ѽ҉ᶬḳ℠
2018-05-08 8:48 ` Christophe-Marie Duquesne
2018-05-08 9:35 ` ѽ҉ᶬḳ℠
2018-05-07 8:24 ` ѽ҉ᶬḳ℠
2018-05-07 8:41 ` Jordan Glover
2018-05-07 9:37 ` Matthias Urlichs
2018-05-07 11:21 ` Jordan Glover
2018-05-07 6:49 ` Kalin KOZHUHAROV
2018-05-08 15:44 Riccardo Berto
2018-05-08 16:23 ` logcabin
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=CAHmME9o4PUH_+DNMC1cWPcRRfDvdeB0k_6bJMgsMMN8JSq51PA@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=vtol@gmx.net \
--cc=wireguard@lists.zx2c4.com \
/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;
as well as URLs for NNTP newsgroup(s).