Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [patch] wg: add support for peer names using a file in userspace
Date: Fri, 8 Dec 2017 05:23:49 +0100	[thread overview]
Message-ID: <CAHmME9pL8+FQv_oAKCFpnZQ6ew1xmoKk-RQqtDHktWARvDXH_w@mail.gmail.com> (raw)
In-Reply-To: <4B7E0154-039F-4008-9C47-C825E1474731@lonnie.abelbeck.com>

Hi Lonnie,

Thanks for sending this to the mailing list. Indeed it got lost in the
fold of disorganized email filters when you sent it to me directly
twice earlier; sorry about that.

I'm not certain this is the right approach -- having wg(8) rely on
fixed filesystem paths, and splitting peer configuration information
across three places (original config file, peer data file, kernel).

I think the way forward for this kind of feature would be what I
proposed in an earlier thread, of attaching it to the kernel object,
just like ifalias does or netfilter's comment target. However, the
question I'm still faced with is -- is this really necessary? I
understand that it's _cool_, and adding bells and whistles is fun and
exciting, but I wonder if there a complete system that would actually
benefit form having this that wouldn't already have a better place to
do it?

Jason

  reply	other threads:[~2017-12-08  4:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 15:31 Lonnie Abelbeck
2017-12-08  4:23 ` Jason A. Donenfeld [this message]
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
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=CAHmME9pL8+FQv_oAKCFpnZQ6ew1xmoKk-RQqtDHktWARvDXH_w@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=lists@lonnie.abelbeck.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).