Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Steffen Vogel <post@steffenvogel.de>
To: <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] wireguard-go/device: add new handshake handler and keylog writer
Date: Sun, 16 Oct 2022 11:35:04 +0200	[thread overview]
Message-ID: <146011B3-5B31-422C-B23E-3FC45969CA90@steffenvogel.de> (raw)
In-Reply-To: <4d-63121e80-3-6ef3e80@7869515>

Does somebody know who the current maintainer of wireguard-go is?

My patch seems to be forgotten ☹

On 04.09.22, 19:00, "WireGuard on behalf of Steffen Vogel" <wireguard-bounces@lists.zx2c4.com on behalf of post@steffenvogel.de> wrote:

    (This path is also tracked as PR: https://github.com/WireGuard/wireguard-go/pull/56)

    This change adds support for a new environment variable 'WG_KEYLOGFILE'
    in resemblance to the 'SSLKEYLOGFILE' environment variable used by
    curl, Chrome & Firefox to log ephemeral TLS encryption keys

    When set, wireguard-go will log ephemeral keys generated during
    each handshake to a file specified by the environment variable in the
    WireGuard key log format.

    The format used is the same as then one generated by the
    extract-handshakes.sh script.

    See also:
    - https://git.zx2c4.com/wireguard-tools/tree/contrib/extract-handshakes
    - https://wiki.wireshark.org/WireGuard#key-log-format
    - https://everything.curl.dev/usingcurl/tls/sslkeylogfile

    Signed-off-by: Steffen Vogel post@steffenvogel.de



      reply	other threads:[~2022-10-16  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02 15:16 Steffen Vogel
2022-10-16  9:35 ` Steffen Vogel [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=146011B3-5B31-422C-B23E-3FC45969CA90@steffenvogel.de \
    --to=post@steffenvogel.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).