WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: CHRIZTOFFER HANSEN <chriztoffer@netravnen.de>
To: Jason@zx2c4.com
Cc: wireguard@lists.zx2c4.com
Subject: Re: [wireguard] Wireguard for Windows - local administrator necessary?
Date: Tue, 3 Dec 2019 22:07:24 +0100
Message-ID: <13b61b9c-0fbd-2588-99b0-b377ce8a4c4f@netravnen.de> (raw)
In-Reply-To: <CAHmME9rjiN_q7yhFtaUybaX+x60qeVJ8+oFTdWtr65yb6CMzqQ@mail.gmail.com>


Jason A. Donenfeld wrote on 27/11/2019 13:29:
> On Wed, Nov 27, 2019 at 10:07 AM Chris Bennett <chris@ceegeebee.com> wrote:
>> However I've found the logged in user needs local Administrator access to activate and de-activate a tunnel.  Is there any way around this?  Is it in the roadmap to remove this requirement?
> 
> No intention of reducing the security of the system, no. WireGuard
> requires administrator access because redirecting an entire machine's
> network traffic is certainly an administrator's task.

What if you this functionality is coded as opt-in, for e.g. a org/corp 
sysadmin to enable for the users, and *not* opt-out?

The the default knob will still be secure, and the sysadmin has the 
conscious possibility to put power in the hand of the users. And it will 
  be the sysadm's choice. Not the team behind pushing the development of 
WireGuard forward, taking a choice on behalf of the consumer/user base.

Chriztoffer
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-26  2:35 Chris Bennett
2019-11-27 12:29 ` Jason A. Donenfeld
2019-12-03 21:07   ` CHRIZTOFFER HANSEN [this message]
2019-12-04  0:35     ` [wireguard] " Reuben Martin

Reply instructions:

You may reply publically 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=13b61b9c-0fbd-2588-99b0-b377ce8a4c4f@netravnen.de \
    --to=chriztoffer@netravnen.de \
    --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

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git