Re: [Openvpn-devel] [PATCH] Support non-ASCII TAP adapter names on Windows

2013-10-22 Thread Josh Cepek
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ACK on this; a local build checks out with all sorts of creative UTF-8 device names I threw at it, including ones with spaces too. - -- Josh Cepek On 10/15/13 04:23, Heiko Hund wrote: > Currently the TAP adapter name is fetched as an OEM string, whic

[Openvpn-devel] [PATCH] Support non-ASCII TAP adapter names on Windows

2013-10-15 Thread Heiko Hund
Currently the TAP adapter name is fetched as an OEM string, which is problematic if it contains non-ASCII characters and is to used with netsh. The logfile also contains these non UTF-8 characters. This patch fetches the name from the registry as UCS-2 and converts it right into UTF-8 before it's