From: Eric Light <eric@ericlight.com>
To: wireguard@lists.zx2c4.com
Subject: Re: [patch] add support for peer names using a file in userspace
Date: Sat, 09 Dec 2017 14:09:50 +1300 [thread overview]
Message-ID: <1512781790.2178482.1199106832.50AF586D@webmail.messagingengine.com> (raw)
In-Reply-To: <CAHmME9r-Vc20LS=bQeNPH8f4+zMjyVNjYW30zX1+5-8vx5Y4cg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
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].
Having it as an attribute of the peer makes sense to me (e.g.
"Description=")... the name really IS an attribute of a peer.
The question is, is wg(8) the right place to put this? I think so, but
only by virtue of the fact that I can't think of anywhere more
appropriate to put it.
Hope that feedback is worth at least two cents :)
--------------------------------------------
Q: Why is this email five sentences or less?
A: http://five.sentenc.es
On Sat, 9 Dec 2017, at 09:39, Jason A. Donenfeld wrote:
>
>
> On Dec 8, 2017 14:00, "Lonnie Abelbeck"
> <lists@lonnie.abelbeck.com> wrote:>>
>> On Dec 8, 2017, at 12:45 PM, Jason A. Donenfeld
>> <Jason@zx2c4.com> wrote:>>
>> I suggested "no spaces" since currently all spaces are stripped in
>> config_read_line()>
> Oh, okay. It's that way mostly out of my own laziness. I wouldn't
> object to making that into a real parser though.> _________________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
[-- Attachment #2: Type: text/html, Size: 2459 bytes --]
next prev parent reply other threads:[~2017-12-09 1:02 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 [this message]
2017-12-09 11:32 ` Matthias Urlichs
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=1512781790.2178482.1199106832.50AF586D@webmail.messagingengine.com \
--to=eric@ericlight.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 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).