From: Peter Wu <peter@lekensteyn.nl>
To: wireguard@lists.zx2c4.com
Subject: Release of Wireshark dissector with decryption support
Date: Fri, 3 Mar 2017 17:08:45 +0100 [thread overview]
Message-ID: <20170303160845.GA29450@al> (raw)
Hi all!
I have been working on a WireGuard dissector for Wireshark with
decryption support for both Transport data and handshake messages.
Since the extract-keys utility included with WG is quite limited (needs
CONFIG_DEVKMEM=y and cannot obtain handshake secrets), I took a
different approach using kprobes and am able to obtain the three
handshake secrets too. (Future work includes obtaining just the
ephemeral keys and then deriving the keys from that.)
For code, documentation, screenshots and sample captures, see
https://github.com/Lekensteyn/wireguard-dissector
Dissection is functionally complete. The main remaining tasks include
adding expert info when the protocol is not being followed and
verification/decryption of Cookie Replies.
--
Kind regards,
Peter Wu
https://lekensteyn.nl
next reply other threads:[~2017-03-03 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 16:08 Peter Wu [this message]
2017-03-03 17:37 ` Jason A. Donenfeld
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=20170303160845.GA29450@al \
--to=peter@lekensteyn.nl \
--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).