From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Hristo Venev <hristo@venev.name>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] Implement reading keys from stdin.
Date: Sat, 8 Feb 2020 23:20:47 +0100 [thread overview]
Message-ID: <CAHmME9owUFjKsW=oGWeziQk8rjPm4cMrArJQ=nDP8+793w5PsA@mail.gmail.com> (raw)
In-Reply-To: <20200207200035.69579-1-hristo@venev.name>
Thank for the patch, and nice hanging with you at FOSDEM.
Trying to get a handle on the use case for this. Is this so that you
can put the private key and the preshared key in a single file
together? Is there a situation where the shell redirection trick
doesn't cut it? For example:
wg set wg0 private-key <(head -n 1 bothkeys) preshared-key <(tail -n 1 bothkeys)
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-02-08 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 20:00 [PATCH] Implement reading keys from stdin Hristo Venev
2020-02-08 22:20 ` Jason A. Donenfeld [this message]
2020-02-09 0:15 ` Hristo Venev
2020-02-14 11:17 ` Jason A. Donenfeld
2020-02-14 23:38 ` Hristo Venev
2020-02-14 11:12 ` Mantas Mikulėnas
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='CAHmME9owUFjKsW=oGWeziQk8rjPm4cMrArJQ=nDP8+793w5PsA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=hristo@venev.name \
--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).