From: Christophe-Marie Duquesne <chmd@chmd.fr>
To: vtol <vtol@gmx.net>
Cc: wireguard <wireguard@lists.zx2c4.com>
Subject: Re: WG interface to ipv4
Date: Mon, 7 May 2018 15:35:39 +0200 [thread overview]
Message-ID: <CAHLp1Y=3n-b2x+51hv2-4w2w4_GdLAwKZ00jhKvPGHg+-PiWPg@mail.gmail.com> (raw)
In-Reply-To: <d8bb14e2-43f6-812b-ad5d-3d7b143ae518@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
On Sun, May 6, 2018 at 9:39 PM, ѽ҉ᶬḳ℠ <vtol@gmx.net> wrote:
> With a thread model considering every piece of software being flawed in
> mind, and with whatever CVE unearthed being a point in case, it should be
> of little surprise that the question of mitigating surface exposure is
> raised. Once WG would gain traction beyond a niche app it is likely to be
> subjected to malicious attacks with increased frequency.
>
There is no need for a nob in wireguard to ensure that the wireguard
traffic goes through a specific interface or is bound to a specific ip
address. You can use iptables if you want to drop packets that are not for
the intended interface / ip address. You can disable ipv6 if you don't want
ipv6. If you think that wireguard could be flawed, why would you trust this
as a wireguard option? If you do not trust it, enforce it from the outside.
[-- Attachment #2: Type: text/html, Size: 1217 bytes --]
next prev parent reply other threads:[~2018-05-07 13:33 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
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 ` Christophe-Marie Duquesne [this message]
2018-05-07 16:34 ` WG interface to ipv4 ѽ҉ᶬḳ℠
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='CAHLp1Y=3n-b2x+51hv2-4w2w4_GdLAwKZ00jhKvPGHg+-PiWPg@mail.gmail.com' \
--to=chmd@chmd.fr \
--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).