From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: ephemeral key extraction
Date: Fri, 2 Mar 2018 14:56:15 +0100 [thread overview]
Message-ID: <CAHmME9pcjsjOTJztgz_XawxUUaOM=GCvs3N9rRvkx_Y8Xzm+-g@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9pPRCTf1MyN9RgPKPYZ2Wscnvrgqq9b1gWhMg5ovTu9Xg@mail.gmail.com>
On Wed, Feb 28, 2018 at 9:11 PM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> For a few days, I'll run a simple netcat server on demo.wireguard.com.
> Try typing `nc demo.wireguard.com 58812` and then connecting to the
> demo box like usual. Basically, it's every cryptographer's girlfriend
> Eve's wildest fantasy. All of the key compromises all of the time!
By popular demand, for a limited time only, coming to a key compromise
situation near you, with no strings attached, in full bitstream
quality, now avid Eves can get a live pcap in addition to the stream
of ephemeral keys above:
Try running `nc demo.wireguard.com 37281`, and piping it to wireshark.
Happy decrypting!
Jason
prev parent reply other threads:[~2018-03-02 13:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 20:11 Jason A. Donenfeld
2018-03-02 13:56 ` Jason A. Donenfeld [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='CAHmME9pcjsjOTJztgz_XawxUUaOM=GCvs3N9rRvkx_Y8Xzm+-g@mail.gmail.com' \
--to=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 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).