Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Manuel Schölling" <manuel.schoelling@gmx.de>
To: wireguard@lists.zx2c4.com
Subject: Reading configuration from stdin
Date: Sun, 10 Dec 2017 13:43:52 +0100	[thread overview]
Message-ID: <1512909832.1336.19.camel@gmx.de> (raw)

Hi,

I am currently working on a NetworkManager plugin for WireGuard in Rust
[1/2].
The plugin has to pass the configuration to the wg tool and I am
wondering if this could be done using interprocess communication.

Would it make sense (aka be secure) if we make it possible to call 'wg
setconf wg0 -' so the wg tool does not read the configuration from a
file but from stdin? Same for 'wg set wg0 private-key -' and 'wg set
wg0 psk -'?

Btw, this NetworkManager plugin should not only work for the regular
WireGuard but also for my wireguard peer-to-peer tool [3] whose
development is currently stalled by a rust bug [4].

This wireguard peer-to-peer tool allows you to use wireguard in
situations where you do not have a static IP and/or you are behind a
NAT.

Anyway, what do you think about reading the configuration from stdin?

Bye,

Manuel


[1] https://github.com/manuels/wg-p2p-nm-plugin
[2] https://github.com/manuels/wg-p2p-nm-plugin/blob/master/Screenshot.
png
[3] https://github.com/manuels/wireguard-p2p
[4] https://github.com/rust-lang/rust/issues/45259

             reply	other threads:[~2017-12-10 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 12:43 Manuel Schölling [this message]
2017-12-11  4:12 ` Aaron Jones
2017-12-11 20:31   ` Manuel Schölling
2017-12-11  4:24 ` Jason A. Donenfeld
2017-12-11 20:36   ` Manuel Schölling

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=1512909832.1336.19.camel@gmx.de \
    --to=manuel.schoelling@gmx.de \
    --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).