Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: jomat+wireguard.io@jmt.gr
Cc: wireguard@lists.zx2c4.com
Subject: Re: Debian-based configuration for wireguard
Date: Tue, 11 Jul 2017 18:19:45 -0400	[thread overview]
Message-ID: <871spmzke6.fsf@fifthhorseman.net> (raw)
In-Reply-To: <71133f541e1824a0eeb5e2e624aa1f2f@jmt.gr>

On Tue 2017-07-11 13:04:40 +0000, jomat+wireguard.io@jmt.gr wrote:
> [ dkg wrote: ]
>>  * it looks to me like configuring a wireguard link this way will
>>    require an entry in /etc/network/interfaces (or interfaces.d) *and* 
>> a
>>    config file in /etc/wireguard/*.conf.  It seems like it would be
>>    cleaner to have all the configuration in one place, no?
>
> /etc/network/interfaces is usually world readable, /etc/wireguard/ not
> as your private keys are stored there.

Good point!  it'd be great to be able to separate the private key
information from the standard network information for that reason; it's
not like people can't inspect the rest of the network config once the
device is configured, so it would be nice to be able to just have the
private key in an isolated file.

        --dkg

  reply	other threads:[~2017-07-11 22:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09 21:30 Baptiste Jonglez
2017-07-09 23:17 ` jomat+wireguard.io
2017-07-10  2:53   ` Jason A. Donenfeld
2017-07-10 19:53     ` Egbert Verhage
2017-07-10 21:20       ` Daniel Kahn Gillmor
2017-07-11  1:59         ` Jason A. Donenfeld
2017-07-11 10:22         ` Egbert Verhage
2017-07-11 13:04         ` jomat+wireguard.io
2017-07-11 22:19           ` Daniel Kahn Gillmor [this message]
2017-07-11 22:48             ` Jason A. Donenfeld
2017-07-11 23:12               ` Daniel Kahn Gillmor
2017-07-10  2:51 ` Jason A. Donenfeld
2017-07-10 20:14 raul

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=871spmzke6.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=jomat+wireguard.io@jmt.gr \
    --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).