-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27/04/12 14:15, Alon Bar-Lev wrote: > 2012/4/27 Samuli Seppänen <sam...@openvpn.net>: >> Il 27.04.2012 12:18, Heiko Hund ha scritto: >>> On Friday 27 April 2012 09:54:15 Samuli Seppänen wrote: >>>> Anyways, I cross-compiled latest "master" with this patch >>>> applied and "bin" and "lib" directories on top of an existing >>>> openvpn-2.3-alpha1 install. The old "bin" directory was >>>> renamed to make sure none of it was used. I then renamed >>>> "openvpn.ovpn" to "ääliö.ovpn" and "ta.key" to "ääliö.key" >>>> using Windows Explorer. Then I updated the configuration file >>>> to point to these files using Notepad (and later Wordpad). >>> Notepad saves UTF-8 files with BOM, which is very uncommon. >>> Maybe that was the problem. I ran into that when I was testing >>> my patch. You might want to try using Notepad++ and save it as >>> UTF-8 without BOM. >>> >>> HTH Heiko >> Saved the configuration file to UTF-8 without BOM - after this I >> got no complaints from OpenVPN-GUI. Launching OpenVPN from the >> command prompt also worked... tls-auth was undefined in the >> config, and openvpn called like this: > > if bom is a problem we should handle it properly in options.c, as > we cannot expect users to understand bom issues. > >> >>> openvpn --config ääliö.ovpn --tls-auth ääliö.key 1 >> >> Only minor issue was that the command prompt displayed funky >> characters instead of the proper ones: >> >> <http://users.utu.fi/sjsepp/cmd2.png> > > Yes. this is OK.
Just so that I understand this more properly. The reason this is okay, is that because cmd.exe is not UTF-8 capable when displaying the log data? kind regards, David Sommerseth -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEARECAAYFAk+iMy8ACgkQDC186MBRfrp8LACeNRzTrcdd8JWyzTEJ3B5Kv1ye iFsAmNM0T3LgxrlJeg3I+7F1aoMSqpw= =PhBy -----END PGP SIGNATURE-----
