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
- Changed state: Started
Original issue reported on code.google.com by
igorradu...@gmail.comon 18 Jun 2014 at 8:07