Hi On Mon, Dec 16, 2019 at 4:31 PM Lev Stipakov <lstipa...@gmail.com> wrote: >> >> I have already said what I think of it. As an admin I wouldn't like to see >> users running processes that elevate to SYSTEM like this. > > > Would it be too much if > > - openvpn.exe process detects that it is not started by interactive service > - interactive service process is running > - wintun is used as --windows-driver >
I think this is possible and in fact I had something like this in mind as well I wrote we could provide an openvpn launcher script. And I would like to do this even if wintun is in use as ability to run openvpn.exe as a regular would be a plus for everyone. > then openvpn behaves as a command-line version of openvpn-gui - connects to > service, which > runs openvpn.exe, and then prints output, received via management interface, > to console? It may be better to redirect the output to the stdout or file as usual so that no user visible changes and easier to implement too. Just keep the process id returned from the service and when the user kills the front-end, terminate the background process started by the service too. This should also allow to run the automatic service as LocalService or a special service user as many services do. Selva > > -- > -Lev _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
