From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: How to verify a wireguard public key?
Date: Fri, 25 Dec 2020 23:16:39 +0100 [thread overview]
Message-ID: <dfec7de6-8f7d-4e89-4e90-3865aa6b7d04@urlichs.de> (raw)
In-Reply-To: <CAB5G8p9nCdxkikyubjfjJ4bB4+9LXNrEbCN+ONfZn28g26WE0Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 337 bytes --]
On 25.12.20 00:42, Adam Stiles wrote:
> "How do I validate Curve25519 public keys?"
You send a handshake packet to the owner of the corresponding private
key and observe whether it accepted it.
The question is, why do you think you need a different/additional way of
verifying the public key?
--
-- Matthias Urlichs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2020-12-25 22:17 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 [this message]
2020-12-26 8:09 ` Nico Schottelius
2020-12-26 9:03 ` Matthias Urlichs
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=dfec7de6-8f7d-4e89-4e90-3865aa6b7d04@urlichs.de \
--to=matthias@urlichs.de \
--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).