From: Yoni Leitersdorf <litelite@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>, alex@alexburke.ca
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Usability issue in MacOS
Date: Sat, 8 Feb 2020 13:51:39 -0800 [thread overview]
Message-ID: <CAJFy1VX4g3Ygf35=VXyUbryyax9ygob8kbSw8GquZ8niW9MTeg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rwuUDDRX1Z9w1ir56ZvYZB-AZcebqJX3BwyNd5wHUx7g@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1161 bytes --]
The original concept behind "On Demand" is to trigger the VPN when it's
needed - specifically when specific domains are being accessed. Indeed,
Apple expanded it to even include interfaces that are connected, SSIDs,
etc, in a non-intuitive way.
However, what makes it somewhat more un-intuitive is the fact that these
checkboxes appear in the main configuration screen for the tunnel. So, one
just simply checks the boxes, thinking "I want VPN to work on-demand on all
of my interfaces". Since, this feature works so oddly (compared to its
name), I would recommend putting it under a separate dialog. In that
dialog, we can explain what this feature does, and also allow for DNS names
to be used, which is the main use case for VPN On Demand.
On Sat, Feb 8, 2020 at 1:37 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> Talk to Apple about that:
>
>
> https://developer.apple.com/documentation/networkextension/personal_vpn/vpn_on_demand_rules
>
> I'm hesitant to stray too far from the analogies that they set up,
> even if this is geared toward developers, because inevitably people
> start googling, and I'd rather them find what they're searching for.
>
[-- Attachment #1.2: Type: text/html, Size: 1658 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-02-08 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 15:50 Yoni Leitersdorf
2020-02-08 21:37 ` Jason A. Donenfeld
2020-02-08 21:51 ` Yoni Leitersdorf [this message]
2020-02-08 21:39 ` Alex Burke
2020-04-05 5:14 Eric Roch
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='CAJFy1VX4g3Ygf35=VXyUbryyax9ygob8kbSw8GquZ8niW9MTeg@mail.gmail.com' \
--to=litelite@gmail.com \
--cc=Jason@zx2c4.com \
--cc=alex@alexburke.ca \
--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).