From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: [patch] add support for peer names using a file in userspace
Date: Sat, 9 Dec 2017 12:32:23 +0100 [thread overview]
Message-ID: <0582b73b-d364-5313-0fc0-2249833509df@urlichs.de> (raw)
In-Reply-To: <1512781790.2178482.1199106832.50AF586D@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 749 bytes --]
On 09.12.2017 02:09, Eric Light wrote:
> For what it's worth, I agree with Lonnie that *something* is necessary.
>
> That said, I don't feel it makes sense in the context of
> [Peer-why_would_this_go_here_its_very_strange].
>
Well … I don't care whether it's named [Peer-foo] or [Peer_bar] or [Peer
baz], though the third option is most appealing IMHO.
I do however care a lot about not having multiple [Peer] sections in the
config file. Automated tools like Ansible cannot deal with
identically-tagged sections. This makes auto-updating my wireguard
configuration unnecessarily difficult.
Thus, if "wg showconf" is intended to output something that can be
reused, then the kernel needs to know about the peer's name.
--
-- Matthias Urlichs
[-- Attachment #2: Type: text/html, Size: 1410 bytes --]
next prev parent reply other threads:[~2017-12-09 11:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 15:31 [patch] wg: " Lonnie Abelbeck
2017-12-08 4:23 ` Jason A. Donenfeld
2017-12-08 4:26 ` Jason A. Donenfeld
2017-12-08 13:42 ` [patch] " Lonnie Abelbeck
2017-12-08 18:45 ` Jason A. Donenfeld
2017-12-08 19:00 ` Lonnie Abelbeck
2017-12-08 20:39 ` Jason A. Donenfeld
2017-12-09 1:09 ` Eric Light
2017-12-09 11:32 ` Matthias Urlichs [this message]
2018-03-01 15:36 ` Damian Kaczkowski
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=0582b73b-d364-5313-0fc0-2249833509df@urlichs.de \
--to=matthias@urlichs.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).