From: Matthias Urlichs <matthias@urlichs.de>
To: Nico Schottelius <nico.schottelius@ungleich.ch>
Cc: wireguard@lists.zx2c4.com
Subject: Re: How to verify a wireguard public key?
Date: Sat, 26 Dec 2020 10:03:13 +0100 [thread overview]
Message-ID: <e1b1c0f0-9262-6612-6d05-8b0f255752fb@urlichs.de> (raw)
In-Reply-To: <875z4p56p7.fsf@ungleich.ch>
[-- Attachment #1.1: Type: text/plain, Size: 605 bytes --]
On 26.12.20 09:09, Nico Schottelius wrote:
> That answer is easy: if you add an incorrect key to your wgX.conf, wg
> setconf will complain and not apply it. And if you are providing
> automated VPNs... well, then this is something you do want to prevent.
Umm, sure, but then the question is why an incorrect key would be sent
through your automated VPN deployment in the first place. And if it
passes the length check but is still corrupted then that's a worse
failure mode than "wg setconf" complaining, 'cause at least you'd notice
the latter immediately.
--
-- Matthias Urlichs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2020-12-26 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 16:00 Nico Schottelius
2020-12-24 23:30 ` Jason A. Donenfeld
2020-12-24 23:42 ` Adam Stiles
2020-12-25 9:10 ` Nico Schottelius
2020-12-25 23:37 ` Matthias May
2020-12-25 23:47 ` Jason A. Donenfeld
2020-12-25 22:16 ` Matthias Urlichs
2020-12-26 8:09 ` Nico Schottelius
2020-12-26 9:03 ` Matthias Urlichs [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=e1b1c0f0-9262-6612-6d05-8b0f255752fb@urlichs.de \
--to=matthias@urlichs.de \
--cc=nico.schottelius@ungleich.ch \
--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).