From: Aaron Jones <aaronmdjones@gmail.com>
To: "Manuel Schölling" <manuel.schoelling@gmx.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Reading configuration from stdin
Date: Mon, 11 Dec 2017 04:12:41 +0000 [thread overview]
Message-ID: <ebc466dc-a1b7-6de9-2e3b-fb94e63f60a6@gmail.com> (raw)
In-Reply-To: <1512909832.1336.19.camel@gmx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 10/12/17 12:43, Manuel Schölling wrote:
> Hi,
>
> Would it make sense (aka be secure) if we make it possible to call
> 'wg setconf wg0 -' so the wg tool does not read the configuration
> from a file but from stdin? Same for 'wg set wg0 private-key -' and
> 'wg set wg0 psk -'?
This should already be possible via `wg setconf wg0 /dev/stdin', no?
Regards,
Aaron Jones
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJaLgWzAAoJEIrwc3SIqzASBtsQAK2rF9J9+Ex7/hu98bLXoeKG
fXR6sU0254Ddre51EA/71Z4QBEFjAROqJyZMnwZE/KkNIRdpX2Xp/lt7w4s/N2zI
btBRydqnsefQlVlbni6Q6Px5F6WjDFLXERXbwTonV0U1f1iel+i55nKs5Ups/WM5
nBlWNepYCO3qZ7ni87C0GO68Z29sEiIPlgS69B4sPeBFg+UW+91TeBh3Cb1Q+JYA
KJhKNrrjMyIpduSF7Rasuu0/LMCF3RwJe1JcO/m+8ftlmu+lzIPfB3z6NMyVBftU
RkcPIuFo09RTsfvBXZRQGJUBXSnNeKJgk0ji25xakwhkTw/LQb3y2uddKRHXIclr
27qnOd1lRPMOYs2co04RiOHMr7yA/+f7bkQfpKQJNyIHtMp2LKZpgDHDnEuOl16n
GrGlaFCiDDWPeO6suOsAmHJMOqLAVgj+L2bAWdO3o5kz6nSsF5Zn3NQLlqwjV+pV
NhvHJgPshGJKin0Styyi+M9Sn1KwXhgoWx9EMZY9mnP58QPl9HxswpBOlZ+Alv5n
aQJqLU/i7wAYotbPREr6EIu/RlaWDYJuTOuoRZU4Hb2TTPnVocjP2nvsH7Mz3AkO
fwe2TfyloUt+DhcIFarjneovqF/Bwasv9C0TAZIeB6nfTfuCrzdbi0cipK2m+y9Y
rC2vzKK0LsSjjpWCsEoF
=03ZW
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-12-11 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-10 12:43 Manuel Schölling
2017-12-11 4:12 ` Aaron Jones [this message]
2017-12-11 20:31 ` Manuel Schölling
2017-12-11 4:24 ` Jason A. Donenfeld
2017-12-11 20:36 ` Manuel Schölling
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=ebc466dc-a1b7-6de9-2e3b-fb94e63f60a6@gmail.com \
--to=aaronmdjones@gmail.com \
--cc=manuel.schoelling@gmx.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).