Message-ID: <4F9A8928.9080703@...515...> Date: Fri, 27 Apr 2012 14:55:20 +0300 From: =?ISO-8859-1?Q?Samuli_Sepp=E4nen?= MIME-Version: 1.0 References: <1332621070-28464-1-git-send-email-alon.barlev@...277...> <4F9A5EB7.902@...515...> <2620278.PZKTmmtf1E@...1526...> In-Reply-To: <2620278.PZKTmmtf1E@...1526...> Subject: Re: [Openvpn-devel] [PATCH] cleanup: windows: convert argv (UCS-2 to UTF-8) at earliest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable To: Heiko Hund Cc: "openvpn-devel@lists.sourceforge.net" Il 27.04.2012 12:18, Heiko Hund ha scritto: > On Friday 27 April 2012 09:54:15 Samuli Sepp=E4nen 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 "=E4=E4li=F6.ovpn" and "ta.key" to >> "=E4=E4li=F6.key" using Windows Explorer. Then I updated the configurati= on >> file to point to these files using Notepad (and later Wordpad). > Notepad saves UTF-8 files with BOM, which is very uncommon. Maybe that wa= s the=20 > problem. I ran into that when I was testing my patch. You might want to t= ry=20 > 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: > openvpn --config =E4=E4li=F6.ovpn --tls-auth =E4=E4li=F6.key 1 Only minor issue was that the command prompt displayed funky characters instead of the proper ones: Thanks for the tip, Heiko! --=20 Samuli Sepp=E4nen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock