<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 09.12.2017 02:09, Eric Light wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1512781790.2178482.1199106832.50AF586D@webmail.messagingengine.com">
<title></title>
<style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
<div>For what it's worth, I agree with Lonnie that *something* is
necessary.<br>
</div>
<div><br>
</div>
<div>That said, I don't feel it makes sense in the context of
[Peer-why_would_this_go_here_its_very_strange].<br>
</div>
<div><br>
</div>
</blockquote>
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.<br>
<br>
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.<br>
<br>
Thus, if "wg showconf" is intended to output something that can be
reused, then the kernel needs to know about the peer's name.<br>
<br>
<pre class="moz-signature" cols="72">--
-- Matthias Urlichs</pre>
</body>
</html>