Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Anatoli <me@anatoli.ws>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Regenerate keypair option for desktop clients
Date: Tue, 5 May 2020 04:52:22 -0300	[thread overview]
Message-ID: <92c23171-a2e0-ba3f-e66c-f5a0a0abad59@anatoli.ws> (raw)

Hi,

Is it possible to add an option to the desktop clients to regenerate the
keypair (on the screen with the statistics about the tunnel, where the
Edit button is located) as in the iOS app?

The rationale is that to configure a client machine an admin usually
sends a config to the user via email or similar, but for obvious
security reasons the keypair in the config should be changed. On iOS we
can ask the user to click on "Regenerate keypair" and send back the new
public key. Quite simple.

On the desktop clients today one should instruct the user to create an
empty config first, copy from there the private key, delete the config,
import the real config and replace there the private key with the
regenerated one. Then send back the public key. Quite cumbersome,
especially for non-advanced users.

Thanks,
Anatoli

                 reply	other threads:[~2020-05-06 10:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=92c23171-a2e0-ba3f-e66c-f5a0a0abad59@anatoli.ws \
    --to=me@anatoli.ws \
    --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).