#67 closed Feature Wish ( fixed )
Certificate CN field with unicode symbols
| Reported by: | forth | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | beta 2.3 |
| Component: | Certificates | Version: | OpenVPN 2.1.2 / 2.1.3 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
| Cc: |
Description
When certificate field CN given in unicode, openvpn replaces all unicode symbols by underscores. So, users with equal CN length needed duplicate-cn openvpn option, because openvpn treats them as equal.
no-name-remapping isn't solving problem.
Change History (3)
comment:1 Changed 14 years ago by
| Priority: | major → minor |
|---|---|
| Type: | Bug / Defect → Feature Wish |
comment:2 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I believe this has been solved in OpenVPN 2.3-alpha releases.
commit 5e86fd93779482b90a191f929edebe414cd78a4f
Author: Heiko Hund <heiko.hund@sophos.com>
Date: Sat Feb 4 12:56:24 2012 +0000
UTF-8 X.509 distinguished names
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\xD0\xB0/O=\xD0\x9A\xD1\x80\xD0\xB5\xD0\xBC\xD0\xBB\xD1\x8C/CN=kreml.ru"
becomes "C=ru, L=Москва, O=Кремль, CN=kreml.ru".
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.
Signed-off-by: Heiko Hund <heiko.hund@sophos.com>
Acked-by: Adriaan de Jong <dejong@fox-it.com>
Acked-by: David Sommerseth <davids@redhat.com>
Signed-off-by: David Sommerseth <davids@redhat.com>
comment:3 Changed 13 years ago by
| Milestone: | → beta 2.3 |
|---|
https://forums.openvpn.net/viewtopic.php?f=4&t=7196