From: "Fredrik Strömberg" <stromberg@mullvad.net>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: potential preshared-key changes
Date: Sun, 23 Apr 2017 13:13:21 +0200 [thread overview]
Message-ID: <CANTUoefkd_GaS2TPD-T3sAYiGxjdXOy3=YtQ2iEsWeCsj810CA@mail.gmail.com> (raw)
In-Reply-To: <1492931136.3430679.953148112.4F826684@webmail.messagingengine.com>
Hi! :)
On Sun, Apr 23, 2017 at 9:05 AM, <crasm@wireguard.1.email.vczf.io> wrote:
> Forgive me in advance if this is a horrible or misinformed idea, but why
> not blake2s the preshared-key with each peer's public key and distribute
> that as a per-peer "preshared" key, mixing it in last? That would reduce
> the risk of key compromise, since each peer would have a unique key and
> the real key is not copied to each peer.
>
If I understand you correctly you're suggesting:
1. Peer PSK = BLAKE2S( "Real PSK" + "Peer's static pubkey" )
2. Mix in the peer's PSK the same way Jason suggests
In practice this is equivalent to the discussed change, and "Peer PSK"
would be the real key, for that peer.
Regards,
Fredrik Stromberg
next prev parent reply other threads:[~2017-04-23 11:04 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 [this message]
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
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='CANTUoefkd_GaS2TPD-T3sAYiGxjdXOy3=YtQ2iEsWeCsj810CA@mail.gmail.com' \
--to=stromberg@mullvad.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).