[patch] add support for peer names using a file in userspace

Matthias Urlichs matthias at urlichs.de
Sat Dec 9 12:32:23 CET 2017

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zx2c4.com/pipermail/wireguard/attachments/20171209/8c019bc8/attachment.html>

More information about the WireGuard mailing list