forked from OpenVPN/openvpn
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
With this option, users can basically undo the changes of the UTF-8 support commit 5e86fd9. It's here for short term compatibility and should be removed again as soon as possible. When OpenSSL is used, the subject strings will be in the proprietary format again. Generally username, X.509 CN, and X.509 subject will again be subject to '_' replacemant, unless the "no-remapping" flag is also specified. That flag ensures compatibility with setups using the --no-name-remapping option, that has been removed in 2.3. [v2: More comments related to compat_flags() added by DS plus using COMPAT_FLAG_QUERY expclit] [v3: Improved the man page entry for --compat-names, after suggestions from Bernhard R. Link] Signed-off-by: Heiko Hund <[email protected]> Signed-off-by: David Sommerseth <[email protected]> Acked-by: Gert Doering <[email protected]> Acked-by: David Sommerseth <[email protected]> Message-Id: [email protected] URL: http://article.gmane.org/gmane.network.openvpn.devel/7053
- Loading branch information
Heiko Hund
authored and
David Sommerseth
committed
Sep 12, 2012
1 parent
5d4f543
commit e7412ca
Showing
6 changed files
with
146 additions
and
9 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3403,6 +3403,58 @@ the authenticated username as the common name, | |
rather than the common name from the client cert. | ||
.\"********************************************************* | ||
.TP | ||
.B \-\-compat\-names [no\-remapping] | ||
Until OpenVPN v2.3 the format of the X.509 Subject fields was formatted | ||
like this: | ||
.IP | ||
.B | ||
/C=US/L=Somewhere/CN=John Doe/[email protected] | ||
.IP | ||
In addition the old behavivour was to remap any character other than | ||
alphanumeric, underscore ('_'), dash ('-'), dot ('.'), and slash ('/') to | ||
underscore ('_'). The X.509 Subject string as returned by the | ||
.B tls_id | ||
environmental variable, could additionally contain colon (':') or equal ('='). | ||
.IP | ||
When using the | ||
.B \-\-compat\-names | ||
option, this old formatting and remapping will be re-enabled again. This is | ||
purely implemented for compatibility reasons when using older plug-ins or | ||
scripts which does not handle the new formatting or UTF-8 characters. | ||
.IP | ||
In OpenVPN v2.3 the formatting of these fields changed into a more | ||
standardised format. It now looks like: | ||
.IP | ||
.B | ||
C=US, L=Somewhere, CN=John Doe, [email protected] | ||
.IP | ||
The new default format in OpenVPN v2.3 also does not do the character remapping | ||
which happened earlier. This new format enables proper support for UTF\-8 | ||
characters in the usernames, X.509 Subject fields and Common Name variables and | ||
it complies to the RFC 2253, UTF\-8 String Representation of Distinguished | ||
Names. | ||
|
||
As a backwards compatibility for the removed \-\-no\-name\-remapping feature in | ||
older OpenVPN versions, the | ||
.B no\-remapping | ||
mode flag can be used with the | ||
.B | ||
\-\-compat\-names | ||
option. | ||
When this mode flag is used, the Common Name, Subject, and username strings are | ||
allowed to include any printable character including space, but excluding | ||
control characters such as tab, newline, and carriage-return. It ensures | ||
compatibility with the | ||
.B \-\-no\-name\-remapping | ||
option of OpenVPN versions before v2.3. | ||
|
||
.B Please note: | ||
This option will not be around for a long time. It is only implemented | ||
to make the transition to the new formatting less intrusive. It will be | ||
removed either in OpenVPN v2.4 or v2.5. So please make sure you start | ||
the process to support the new formatting as soon as possible. | ||
.\"********************************************************* | ||
.TP | ||
.B \-\-port-share host port [dir] | ||
When run in TCP server mode, share the OpenVPN port with | ||
another application, such as an HTTPS server. If OpenVPN | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters