From: Riccardo Berto <riccardo@rcrdbrt.com>
To: wireguard@lists.zx2c4.com
Subject: Re: WG interface to ipv4
Date: Tue, 08 May 2018 17:44:56 +0200 [thread overview]
Message-ID: <4f1f154f85bb01204c883e37e41eba86@rcrdbrt.com> (raw)
> The current concept of WG has indeed certain pros over other VPN
> solutions, but like most everything else in life, it has its cons too
> and it will be determined by the user what suits best. Time will tell
> the adoption/penetration level of WG is achieving. For me unfortunately
> the cons (not just what is mentioned in this thread) are outweighing
> the
> pros in WG's current state and thus departing from WG for the time
> being
> but keeping an eye on future developments.
If the cons of WireGuard are that it gives the users less freedom to
make mistakes, then I'm all for it.
I don't really get why the iface bindings should be accomplished at the
WireGuard level. If I get it correctly, it won't be safer than it
already is.
WireGuard just has to provide a secure and standard network interface.
There are other full-featured, clogged VPNs out there that can even make
you the coffee, I'd like WireGuard to stand out and stick to the
original "UNIX tools philosophy": do one thing and do it well.
next reply other threads:[~2018-05-08 15:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 15:44 Riccardo Berto [this message]
2018-05-08 16:23 ` WG interface to ipv4 logcabin
-- strict thread matches above, loose matches on Subject: below --
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
2018-05-06 7:31 ` ѽ҉ᶬḳ℠
2018-05-06 9:00 ` Matthias Urlichs
2018-05-06 9:26 ` ѽ҉ᶬḳ℠
2018-05-06 1:21 ` 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-07 13:35 ` 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
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=4f1f154f85bb01204c883e37e41eba86@rcrdbrt.com \
--to=riccardo@rcrdbrt.com \
--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