From: Julian Orth <ju.orth@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Should setting the listen-port require CAP_SYS_ADMIN in the socket namespace?
Date: Sun, 9 Sep 2018 11:40:32 +0200 [thread overview]
Message-ID: <cbe7e13a-3155-ded7-9dc1-3c8f467d909b@gmail.com> (raw)
In-Reply-To: <dd90475d-b9be-95a7-d23d-9d9c89cb4f2c@gmail.com>
To be clear: The solution described for the transit-net case also applies to
the listen-port case:
Trying to change listen-port and/or transit-net should require CAP_SYS_ADMIN
in the transit namespace unless the user also proves access to that namespace
by passing an UDP socket from that namespace in the same call.
prev parent reply other threads:[~2018-09-09 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 9:13 Should setting the listen-port require CAP_SYS_ADMIN in the socket namespace? Julian Orth
2018-09-09 9:40 ` Julian Orth [this message]
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=cbe7e13a-3155-ded7-9dc1-3c8f467d909b@gmail.com \
--to=ju.orth@gmail.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).