Opened 4 years ago

Closed 4 years ago

#1318 closed Bug / Defect (fixed)

Using wintun by running openvpn.exe as SYSTEM does not work

Reported by: Selva Nair Owned by:
Priority: major Milestone:
Component: Generic / unclassified Version: OpenVPN 2.5.0 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc: tct, Gert Döring, Samuli Seppänen


When run without using the interactive service opening wintum device errors as expected, and the error message suggests to run as SYSTEM. However, when run as SYSTEM (either from automatic service or using psexec etc.) it results in the same FATAL error. It seems running interactively or from the automatic service as SYSTEM is not yet supported.

Change History (5)

comment:1 Changed 4 years ago by tct

Cc: tct Gert Döring added

comment:2 Changed 4 years ago by tct

@selva - you don't get updates unless you CC or comment.

comment:3 Changed 4 years ago by tct

Cc: Samuli Seppänen added

comment:5 Changed 4 years ago by Gert Döring

Resolution: fixed
Status: newclosed

commit ed47c097db63f8334f32bf9482da488928ff909b (master)
commit f4761dd12ec5eb10a5897ecb7dc427f54a9b0769 (release/2.5)
Author: Lev Stipakov <lev@…>
Date: Wed Aug 19 10:07:46 2020 +0300

tun.c: enable using wintun driver under SYSTEM

Commit 6d19775a468 has removed SYSTEM elevation hack,
but introduced regression - inability to use wintun without
interactive service.

Proceed with ring buffers registration even if iservice is unavailable
and display relevant error message.

Trac: #1318

Signed-off-by: Lev Stipakov <lev@…>
Acked-by: Selva Nair <selva.nair@…>

Note: See TracTickets for help on using tickets.