Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Neutron <dotneutron@protonmail.ch>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] embeddable-dll-service: add ability to derive public key from private key
Date: Tue, 10 Aug 2021 21:13:06 +0000	[thread overview]
Message-ID: <7-v7jwwWMXai6l5Uqxgo8UjeuKNOvY2FDx4rsGB1yrAHkfDqrGGfoLOIHQuJuTBJ0HIpmxlqTTFJgWqbGDn5eFT-7bLT8D60enB3pVrc-2o=@protonmail.ch> (raw)
In-Reply-To: <CAHmME9oc2yoSjuh+Mkv_ERTLSocoRDF1Lh4M6HrciRPNqRBx7w@mail.gmail.com>

Hey,

I started working on a C# WPF client based on the reference implementation you provided. I made it so the tunnel configurations can be added or edited via a custom form much alike the one of wg-android. Since I'm only storing the private key in the interface section of a config file, I need to be able to derive the public key and display it to the user.

As a personal example, I'm using Mullvad's wg configurations to test it. I'm able to export all configurations for their servers, for a given private key. I'm left with the typical wg conf files. When I fill in the details for a tunnel configuration in the client I created, I want to be able to write in the private key and have it generate the public key automatically. This is the behavior of wg-android.

Adding that method, rebuilding the dll and invoking it from C# worked like a charm, so I thought it might help other people as well. It is a convenience method for anyone who wants to create a client of their own.

Neutron

      reply	other threads:[~2021-08-10 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 20:29 dotneutron
2021-08-10 20:38 ` Jason A. Donenfeld
2021-08-10 21:13   ` Neutron [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='7-v7jwwWMXai6l5Uqxgo8UjeuKNOvY2FDx4rsGB1yrAHkfDqrGGfoLOIHQuJuTBJ0HIpmxlqTTFJgWqbGDn5eFT-7bLT8D60enB3pVrc-2o=@protonmail.ch' \
    --to=dotneutron@protonmail.ch \
    --cc=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).