Android app whitelist/blacklist feature
eric at bluelinelabs.com
Tue Jul 3 04:27:02 CEST 2018
I was originally thinking the new fragment would be a per-tunnel thing (set
when you create the tunnel or edit it), but you’re right - making it a
general setting likely makes a whole lot more sense. I can’t think of any
use-cases for different tunnels handling different apps.
On July 2, 2018 at 9:21:23 PM, Jason A. Donenfeld (jason at zx2c4.com) wrote:
Sorry for not responding earlier when you sent this to me directly.
I'm glad you sent it here and Samuel caught it, so your nice idea
won't go to waste.
On Tue, Jul 3, 2018 at 2:22 AM Eric Kuck <eric at bluelinelabs.com> wrote:
> If I were to do the work I initially proposed (new fragment + GoBackend
implementation), would this be enough to get merged?
No, but I can write the C part and just provide you with some sane
interface for passing off the relevant information to wg-quick. Send
me offlist an SSH key, and I'll give you commit access to branches
that begin with `ek/`.
> My proposal is to add another Fragment that’s just a list of all apps
installed on the phone with check boxes next to them.
How would one get to the Fragment? From the overflow menu, or from the
settings? I suspect the settings would be a more natural place for it.
Or were you thinking that this would actually be part of each
individual tunnel profile, stored within the configuration for the
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the WireGuard