Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [TOOL] wg-config graduates to src/tools, becomes wg-auto-config
Date: Tue, 03 Jan 2017 01:46:58 -0500	[thread overview]
Message-ID: <87tw9god25.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <CAHmME9q1RQ_Z3tikOkOECsw5xNx5Mttwm5=MPV7PRqu+DcipkA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

On Mon 2017-01-02 10:17:30 -0500, Jason A. Donenfeld wrote:
> On Mon, Jan 2, 2017 at 5:57 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>> Check out the man page, read the script --
>> https://git.zx2c4.com/WireGuard/tree/src/tools/wg-auto-config -- and
>> please let me know what you think before I cut the next snapshot.
> Renamed:
> https://git.zx2c4.com/WireGuard/tree/src/tools/wg-auto-config.bash

debian is unlikely to install this if it is expected to be named with a
.bash suffix:

  https://www.debian.org/doc/debian-policy/ch-files.html#s-scripts

>>> When scripts are installed into a directory in the system PATH, the
>>> script name should not include an extension such as .sh or .pl that
>>> denotes the scripting language currently used to implement it.


That said, i'm not sure what you want with this.  If the ultimate goal
is to have systemd-style .network files, you should ask for these
changes in systemd itself.  That's likely the cleanest approach.  If you
do this, please post a link here to the systemd github issue or pull
request. :)

If it's just "we want a configuration for wg, but with some common/handy
wrappers around /bin/ip", you could (a) fork and exec ip from wg itself
when running "wg setconf", or (b) name the wrapper something like
/usr/bin/wg+ip 

        --dkg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-01-03  6:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02  4:57 Jason A. Donenfeld
2017-01-02 14:49 ` Jason A. Donenfeld
2017-01-02 15:17 ` Jason A. Donenfeld
2017-01-03  6:46   ` Daniel Kahn Gillmor [this message]
2017-01-02  6:48 Anonymous Anonymous
2017-01-03  6:57 Jason A. Donenfeld
2017-01-03 21:10 ` Jason A. Donenfeld
2017-01-04 19:21   ` Jason A. Donenfeld

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=87tw9god25.fsf@alice.fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --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).