From: Eisfunke <nicolas@eisfunke.com>
To: wireguard@lists.zx2c4.com
Cc: Brian Candler <b.candler@pobox.com>
Subject: Re: Reflections on WireGuard Design Goals
Date: Fri, 10 Aug 2018 16:42:15 +0200 [thread overview]
Message-ID: <1898878.xtpBxs3Iqk@miranda> (raw)
In-Reply-To: <b66a15d1-c4f1-78a5-cf5a-4d2a4ca9ce54@pobox.com>
Hello together,
> In the absence of that, it would be nice if the private key which is
> stored on the laptop were encrypted with a passphrase. Simplest option
> may be to extend wg-quick so that the entire config file can be
> pgp-encrypted.
one can already do that via the wg-quick PostUp hook, check out the Arch Linux
wiki:
https://wiki.archlinux.org/index.php/
WireGuard#Store_private_keys_in_encrypted_form
The example is using pass, switching it for direct GPG (or keepassxc or
anything, really) should be easily possible.
Considering that possibility, I don't think adding GnuPG directly into
Wireguard would be a good idea. It would just add complexity for little to no
benefit.
Greetings,
NIcolas Lenz
next prev parent reply other threads:[~2018-08-10 14:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1318.1533866648.2201.wireguard@lists.zx2c4.com>
2018-08-10 13:35 ` Reflections on WireGuard Design Goals Brian Candler
2018-08-10 14:09 ` Matthias Urlichs
2018-08-10 14:09 ` Kalin KOZHUHAROV
2018-08-10 14:42 ` Eisfunke [this message]
2018-08-10 14:47 ` Konstantin Ryabitsev
2018-08-10 15:03 ` Roman Mamedov
2018-08-10 16:03 ` Brian Candler
2018-08-10 16:38 ` Kalin KOZHUHAROV
2018-08-10 16:40 ` jungle Boogie
2018-08-10 17:12 ` Aaron Jones
2018-08-10 17:25 ` jungle Boogie
2018-08-10 20:15 ` em12345
2018-08-10 23:07 ` Reuben Martin
2018-08-11 19:18 ` Jason A. Donenfeld
2018-08-11 22:52 ` Luiz Angelo Daros de Luca
2018-08-12 0:15 ` Aaron Jones
2018-08-12 0:46 ` Jason A. Donenfeld
2018-08-12 1:07 ` Aaron Jones
2018-08-09 21:52 Jason A. Donenfeld
2018-08-10 15:19 ` nicolas prochazka
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=1898878.xtpBxs3Iqk@miranda \
--to=nicolas@eisfunke.com \
--cc=b.candler@pobox.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).