On Fri, Jun 28, 2019 at 5:03 PM Gert Doering <g...@greenie.muc.de> wrote:
> Hi,
> On Fri, Jun 28, 2019 at 04:51:47PM -0400, Selva Nair wrote:
> > Would that mean we can assume that always allowing all users access to
> > the tap (say, using the service to open it) would not be a regression?
> > Or are there folks who use local builds of the driver and expect
> > openvpn.exe to respect that setting?
> The whole permission model for openvpn on Windows has been funky at
> best "forever" - open tap device and setup IPv4 address by means of
> DHCP could be done "by everyone", while installing routes or setting
> up IPv6 then failed for non-Admin accounts...
> I'm not exactly sure what you are proposing, but aligning this with
> wintun and using the service to get access to tap6-windows sounds
> like a reasonable plan.

That's what lev's patch would do, but it wont respect the registry key
which is "supposed" to toggle non-admin access to tap-windows6
adapters on and off.

> With a registry key to re-enable "full
> access as today", for compat reasons.

For some reason that registry key appears to be doing nothing in
current versions of tap-windows6. I know this is confusing...


Openvpn-devel mailing list

Reply via email to