From: "Jason A. Donenfeld" <Jason@zx2c4.com> To: Samuel Holland <firstname.lastname@example.org> Cc: Eric Kuck <email@example.com>, WireGuard mailing list <firstname.lastname@example.org> Subject: Re: Android app whitelist/blacklist feature Date: Tue, 3 Jul 2018 20:17:11 +0200 Message-ID: <CAHmME9qAUveJi6of9TMb_Owffsy-SX+4pQyDMHaz=6COE2CYxQ@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Tue, Jul 3, 2018 at 8:12 PM Samuel Holland <firstname.lastname@example.org> wrote: > Right, trying to make it a global setting requires either some sort of > out-of-band way to pass the information to wg-quick, or rewriting the > configuration file every time the tunnel is brought up. > > Since from netd's point of view, this is a per-network setting anyway, I agree > it makes sense to configure it per-tunnel. ExemptedApplications works as a > configuration key, though I prefer ExcludedApplications--the application isn't > just not required to use the tunnel, it's not allowed to use the tunnel. > > In that case, here are my UI suggestions: > - Add a button in the editor that switches to a fragment or pops up a Dialog > similar to a MultiSelectListPreference. > - For consistency, checked means excluded -- everything defaults to unchecked. > - The package names of excluded apps are put in the > com.wireguard.config.Interface, and wg-quick handles package name to uid > translation. > > How does that sound? All of that sounds right-on to me, and I think you're right that ExcludedApplications is the better key. (This also provides a good basis for later adding a "ExcludeLocalNetwork" option.) Eric's git access should be all setup now, so we can watch the commits coming on in.
next prev parent reply index Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-02 20:35 Eric Kuck 2018-07-02 21:43 ` Samuel Holland 2018-07-03 0:22 ` Eric Kuck 2018-07-03 2:21 ` Jason A. Donenfeld 2018-07-03 2:27 ` Eric Kuck 2018-07-03 2:31 ` Jason A. Donenfeld 2018-07-03 18:12 ` Samuel Holland 2018-07-03 18:17 ` Jason A. Donenfeld [this message] 2018-07-04 22:19 ` Eric Kuck 2018-07-05 13:23 ` Jason A. Donenfeld 2018-07-05 13:24 ` Jason A. Donenfeld
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='CAHmME9qAUveJi6of9TMb_Owffsy-SX+4pQyDMHaz=6COE2CYxQ@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /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 \ email@example.com firstname.lastname@example.org public-inbox-index wireguard 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