Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: potential preshared-key changes
Date: Fri, 28 Apr 2017 12:15:05 +0200	[thread overview]
Message-ID: <CAKXLc7cVeDy+nXB13wWotS=s-VCFMGiUK3U2AgEaYhQxMiF5jw@mail.gmail.com> (raw)
In-Reply-To: <24fd775a-38aa-d6fa-476f-95cc734d990d@hall-andersen.dk>

I finally read through all the thread :-D

(and very good write-up, Mathias!)

Obeying the KISS principle, while erring on security should lead to
"per-client PSK", the proposed method.

I see some scenarios where the current method (per-iface) works
better, mainly in small private VPNs, usually temporary and all
trusting each other; in such cases identity hiding is not an issue and
simple initial setup (one PSK) is a plus.
( think a bunch of short-lived VPC instances, started/owned by single person)

To eat the cake and have it whole, supporting both methods MAY be
possible, iff (=if-and-only-if) this does not introduce lots of
complexity in code.

Thinking about code, how would that be implemented, how do we define user?
I am wondering what happens after Alice establishes a connection to
SERVER_1 with PSK_A from IP_1:
* then someone (Eve?) establishes another connection with (stolen)
PSK_A from IP_2 ? -> log or ignore
* then Bob establishes another connection with own PSK_B from IP_1
(same company GW)? -> hopefully possible!

I guess part of the design of WG is to not keep state or logs, so
those will "simply work" (TM) :-D

Regards,
Kalin.

      reply	other threads:[~2017-04-28 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-22 22:22 Jason A. Donenfeld
2017-04-23  7:05 ` crasm
2017-04-23 11:13   ` Fredrik Strömberg
2017-04-23 19:05     ` crasm
2017-04-23 10:49 ` Fredrik Strömberg
2017-04-28  9:24 ` Mathias
2017-04-28 10:15   ` Kalin KOZHUHAROV [this message]

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='CAKXLc7cVeDy+nXB13wWotS=s-VCFMGiUK3U2AgEaYhQxMiF5jw@mail.gmail.com' \
    --to=me.kalin@gmail.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;
as well as URLs for NNTP newsgroup(s).