From: Hristo Venev <hristo@venev.name>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] Implement reading keys from stdin.
Date: Fri, 14 Feb 2020 23:38:48 +0000 [thread overview]
Message-ID: <a7607bbade0e788d6476717caa5806c233131e2f.camel@venev.name> (raw)
In-Reply-To: <CAHmME9prE9oe4DX7dH6=UpnbBSE8yk6WN5epWxw7UuD_w7a+pQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]
On Fri, 2020-02-14 at 12:17 +0100, Jason A. Donenfeld wrote:
> Except the command line arguments have length limits you'll hit
> anyway. Wouldn't the better way to do this be passing a config file
> to
> `wg setconf wg0 /dev/stdin`?
Yes, they would be better. However each command has slight
inefficiencies for my usecase:
- `wg setconf` removes the endpoints of peers that don't have a static
endpoint address
- `wg addconf` cannot remove peers
- `wg syncconf` needs to be given the exact allowed IPs of all peers
it has to keep, not just the ones that have changed. It will also
remove all peers that were added manually by the user (and not by my
daemon).
For now I will either use `wg syncconf`, or maybe `wg addconf` +
multiple `wg set peer remove`.
I've been thinking, how stable is the IPC protocol? It might be nice to
have a tool/daemon/something that makes it possible to use the protocol
to configure devices that natively use netlink or OpenBSD ioctls.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-02-14 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 20:00 [PATCH] Implement reading keys from stdin Hristo Venev
2020-02-08 22:20 ` Jason A. Donenfeld
2020-02-09 0:15 ` Hristo Venev
2020-02-14 11:17 ` Jason A. Donenfeld
2020-02-14 23:38 ` Hristo Venev [this message]
2020-02-14 11:12 ` Mantas Mikulėnas
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=a7607bbade0e788d6476717caa5806c233131e2f.camel@venev.name \
--to=hristo@venev.name \
--cc=Jason@zx2c4.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).