search

taikoo / tunnelblick

Automatically exported from code.google.com/p/tunnelblick
0 stars 0 forks source link

Problem with #249

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
NOTE: We suggest that you post on the Tunnelblick Discussion Group before
submitting an "Issue". (http://groups.google.com/group/tunnelblick-discuss)

What steps will reproduce the problem?
1. I tried to establish OpenVPN connection throughout different TunnelBlick 3.4 
beta versions
2. I have OPENVPN conf and cert files
3. Every time I obtain ERROR with comment Line 1 of the file contains a 
non-printable character (0xC3) which is not allowed

What is the expected output?
Establishing VPN Connection

What do you see instead?
*Tunnelblick: OS X 10.9.3; Tunnelblick 3.4beta16 (build 3679); prior version 
3.4beta20 (build 3727); Admin user

Last sentences of Console log are:

2014-06-18 09:48:38 Tunnelblick[61245] Configuration installer: CR characters 
are being removed or replaced with LF characters in the installed copy of 
/Users/igorradusinovic/Desktop/Proba.tblk/openvpn-vwall-ca.crt
2014-06-18 09:48:38 Tunnelblick[61245] Configuration installer: CR characters 
are being removed or replaced with LF characters in the installed copy of 
/Users/igorradusinovic/Desktop/Proba.tblk/openvpn-vwall.ovpn
2014-06-18 09:48:38 Tunnelblick[61245] Configuration installer: Failed to parse 
configuration path 
'/private/var/folders/bd/fj7h1db97w15d9qnxtlrb2br0000gn/T/TunnelblickTemporaryDo
tTblk-wvMDlI/Proba.tblk/Contents/Resources/config.ovpn':
                                       Line 1 of the file contains a non-printable character (0xC3) which is not allowed

What version of Tunnelblick are you using? On what version of OS X?
I tried with beta 28, 22, 16, 08, 04, 02, 
I used OS X 10.9.3 (Darwin 13.2.0)

Please provide any additional information below. Please include your
configuration file and the contents of the OpenVPN Log window (including
the first few lines with version information), but remember to remove any
sensitive information such as IP addresses.

Original issue reported on code.google.com by igorradu...@gmail.com on 18 Jun 2014 at 8:07

GoogleCodeExporter commented 9 years ago 
Your configuration file is either corrupt or contains one or more Unicode 
characters outside of a comment or quoted string.

Tunnelblick allows non-ASCII characters in a configuration file only in 
comments and quoted strings. This restriction that means that (for example) the 
valid OpenVPN option
     key лев.pem
must be changed to
     key 'лев.pem'
or
     key "лев.pem"
to work in Tunnelblick.

The reason for this restriction is pragmatism: most of the time, OpenVPN 
configuration files are "plain text" files, which do not contain characters 
with codes higher than 0x7E, and the presence of other characters usually means 
that the file has been corrupted. So most of the time, Tunnelblick will 
correctly diagnose a problem and alert the user. Such corruption (or the use of 
a "rich text" file, which this also detects) has been the cause of many 
problems discussed on the Tunnelblick Discussion Group.

_HOWEVER_, in doing testing to create this response, I found a DIFFERENT BUG 
which incorrectly decodes Unicode characters within such a quoted string. This 
causes Tunnelblick to be unable to find files such as 'лев.pem', so 
attempting to install an OpenVPN configuration file with
     key 'лев.pem'
will fail because the file will not be found because Tunnelblick is looking for 
a file with a different name.

I have created a fix for this and expect to commit it to the source repository 
later today.

The workaround (until this bug is fixed) is to use only ASCII filenames.

I have marked this Issue "Started", meaning that work has started on fixing the 
"different" bug (not decoding Unicode characters in quoted strings properly).

At this point, I do not plan to remove the restriction that limits non-ASCII 
characters to comments and quoted strings, although I am open to discussion 
about doing so.

Original comment by jkbull...@gmail.com on 18 Jun 2014 at 12:07

GoogleCodeExporter commented 9 years ago 
I found problem. Problem was in .crt file. It didn't start with -

Original comment by igorradu...@gmail.com on 19 Jun 2014 at 11:55

GoogleCodeExporter commented 9 years ago 
The latest release (3.4beta30) fixes the problem with Unicode characters inside 
quotes in configuration files.

Original comment by jkbull...@gmail.com on 11 Jul 2014 at 12:22