Hi, On Tue, Aug 18, 2020 at 12:06:18AM -0300, Rafael Gava wrote: > 2020-08-17 19:15:39 us=424470 ERROR: Wintun requires SYSTEM privileges and > therefore should be used with interactive service. If you want to use > openvpn from the command line, you need to do SYSTEM elevation yourself > (for example with psexec).
This can also happen if you run the GUI with admin privs (because then
it will not use the iservice *but* openvpn needs *more* privs than
"just administrator", and wintun can not be used at all).
[..]
> 1) Is there any problem in using openvpn with the wintun interface from an
> unsigned built release?
> 2) Is there any problem with wintun in using an unsigned nsis installer
> than the .msi one?
Not that I'm aware. This looks more like "iservice not being used due
to admin privs when running the GUI".
You can crosscheck this fairly easy - if wintun does not work with the
message above, try running with the old tun/tap driver. If that works,
and you see successful "netsh" commands in the log to set up routing, you
are running with admin privs.
> 3) I'm also trying to generate a msi installer with vagrant msibuilder but
> I'm getting the following error:
I can't say anything about that, sorry...
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany [email protected]
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-devel
