From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Debian-based configuration for wireguard
Date: Tue, 11 Jul 2017 19:12:09 -0400 [thread overview]
Message-ID: <87shi2y3ee.fsf@fifthhorseman.net> (raw)
In-Reply-To: <CAHmME9qAig60WBrjiz=se=B9zhBfhgMOma17MuiQPGdfs+UgRA@mail.gmail.com>
On Wed 2017-07-12 00:48:59 +0200, Jason A. Donenfeld wrote:
> It is for this reason that wg(8)'s private-key and preshared-key
> arguments take a file to the key, not the actual key itself.
Right. but the ifupdown configuration that Egbert has proposed tries to
pull some info from the /etc/network/interfaces stanza and then some
other info from a wireguard configuration file. To a novice user it
looks pretty confusing because the split seems arbitrary.
So the extension to ifupdown should really take just the path to the key
file as an extra argument, not a path to a full wg(8) conf file. I
agree with Egbert that this patch isn't ready for integration with
ifupdown, unfortunately.
--dkg
next prev parent reply other threads:[~2017-07-11 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 21:30 Debian-based configuration for wireguard Baptiste Jonglez
2017-07-09 23:17 ` jomat+wireguard.io
2017-07-10 2:53 ` Jason A. Donenfeld
2017-07-10 19:53 ` Egbert Verhage
2017-07-10 21:20 ` Daniel Kahn Gillmor
2017-07-11 1:59 ` Jason A. Donenfeld
2017-07-11 10:22 ` Egbert Verhage
2017-07-11 13:04 ` jomat+wireguard.io
2017-07-11 22:19 ` Daniel Kahn Gillmor
2017-07-11 22:48 ` Jason A. Donenfeld
2017-07-11 23:12 ` Daniel Kahn Gillmor [this message]
2017-07-10 2:51 ` Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2017-07-10 20:14 raul
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=87shi2y3ee.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.