Hi,
On Sat, Feb 04, 2012 at 12:56:24PM +, Heiko Hund wrote:
> Since the specific character classes for X.509 names are removed, the
> "no-name-remapping" configuration option has no use anymore and is removed
> as well.
--no-name-remapping appears again somewhat further down in openvpn.8,
we
Hi list,
On Saturday 04 February 2012 12:56:24 Heiko Hund wrote:
> The UTF-8 support that came with commit 2627335 does allow international
> usernames and passwords. This patch introduces UTF-8 support for X.509 DNs.
> Additionally, instead of using the legacy openssl format, DNs are now
> displa
The UTF-8 support that came with commit 2627335 does allow international
usernames and passwords. This patch introduces UTF-8 support for X.509 DNs.
Additionally, instead of using the legacy openssl format, DNs are now
displayed in RFC 2253 format; "/C=ru/L=\xD0\x9C\xD0\xBE\xD1\x81\xD0\xBA\xD0
\xB2
On Thu, Nov 24, 2011 at 1:42 PM, Heiko Hund wrote:
> On Wednesday 23 November 2011 17:48:54 Alon Bar-Lev wrote:
>> Yes, there are many none unicode environments, and I am not sure what
>> this patch will behave in windows environment as it is SCS-2 not
>> UTF-8.
It is UCS-2 not UCS-16.
>
> I agr
On Wednesday 23 November 2011 17:48:54 Alon Bar-Lev wrote:
> Yes, there are many none unicode environments, and I am not sure what
> this patch will behave in windows environment as it is SCS-2 not
> UTF-8.
I agree on the UCS-16 environment in Windows. Will post a patch for that soon,
as I'm almo
On Wed, Nov 23, 2011 at 5:14 PM, Heiko Hund wrote:
> On Wednesday 23 November 2011 14:53:06 Alon Bar-Lev wrote:
>> As this is inserted into environment, what happens if locale is not
>> unicode enabled?
>
> Then the script will receive funny looking strings depending on your locale's
> code page.
On Wednesday 23 November 2011 14:53:06 Alon Bar-Lev wrote:
> As this is inserted into environment, what happens if locale is not
> unicode enabled?
Then the script will receive funny looking strings depending on your locale's
code page. However, this is nothing that's being introduced with this p
As this is inserted into environment, what happens if locale is not
unicode enabled?
I think this may break some configurations.
On Wed, Nov 23, 2011 at 4:14 PM, Heiko Hund wrote:
> The UTF-8 support that came with commit 2627335 does allow international
> usernames and passwords. This patch intr
The UTF-8 support that came with commit 2627335 does allow international
usernames and passwords. This patch introduces UTF-8 support for X.509 DNs.
Additionally, instead of using the legacy openssl format, DNs are now
displayed in RFC 2253 format; "/C=ru/L=\xD0\x9C\xD0\xBE\xD1\x81\xD0\xBA\xD0
\xB2
