From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] auth-only wireguard
Date: Thu, 6 Oct 2016 14:27:43 -0500 [thread overview]
Message-ID: <20161006192743.GA12972@wolff.to> (raw)
In-Reply-To: <CAHmME9qj9AARx7S6RsyCnWYN4fJizeHfgeqW4zmFtGahLs--pg@mail.gmail.com>
On Thu, Oct 06, 2016 at 19:32:36 +0200,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>On Thu, Oct 6, 2016 at 5:03 PM, Bruno Wolff III <bruno@wolff.to> wrote:
>> Without encryption you authentication won't be useful against attackers that
>> can modify packets or insert packets with the source address of your
>> contact.
>
>Either I've misunderstood you, or this is completely inaccurate.
>
>What do you mean exactly?
Someone able to watch and modify traffic can wait for authentication to occur
and then take over the connection. So you don't know you are still
communicating with the party that did the authentication. You need something
protecting message integrity which is normally based on encryption, but I
think there might be ways to do that with just hashing.
next prev parent reply other threads:[~2016-10-06 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 2:12 [WireGuard] auth-only wireguard Jehan Tremback
2016-10-06 5:48 ` Jason A. Donenfeld
2016-10-06 15:03 ` Bruno Wolff III
2016-10-06 16:34 ` Jehan Tremback
2016-10-06 17:35 ` Jason A. Donenfeld
2016-10-06 17:42 ` Alex Xu
2016-10-06 19:34 ` Jehan Tremback
2016-10-06 17:32 ` Jason A. Donenfeld
2016-10-06 19:27 ` Bruno Wolff III [this message]
2016-10-06 20:43 ` Jason A. Donenfeld
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=20161006192743.GA12972@wolff.to \
--to=bruno@wolff.to \
--cc=Jason@zx2c4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.