This option was removed in 2.5 (commit
c3f565f059) but still showed
up in the ``openvpn --help`` text and in a Q&A section of the man page.
Change-Id: Ib15bd4148872db39a4c8291796a5da211bb20a87
Signed-off-by: Gert Doering <gert@greenie.muc.de>
Acked-by: Frank Lichtenheld <frank@lichtenheld.com>
Gerrit URL: https://gerrit.openvpn.net/c/openvpn/+/1411
Message-Id: <
20251127115737.3598-1-gert@greenie.muc.de>
URL: https://www.mail-archive.com/openvpn-devel@lists.sourceforge.net/msg34754.html
Signed-off-by: Gert Doering <gert@greenie.muc.de>
a filename, etc.
*Q: Can string remapping be disabled?*
- Yes, by using the ``--no-name-remapping`` option, however this
- should be considered an advanced option.
+ No. The options ``--no-name-remapping`` and ``--compat-names`` have
+ been removed in 2.5 because they were considered too insecure.
Here is a brief rundown of OpenVPN's current string types and the
permitted character class for each string:
" for generated tokens can be set.\n"
"--auth-user-pass-optional : Allow connections by clients that don't\n"
" specify a username/password.\n"
- "--no-name-remapping : (DEPRECATED) Allow Common Name and X509 Subject to include\n"
- " any printable character.\n"
"--client-to-client : Internally route client-to-client traffic.\n"
"--duplicate-cn : Allow multiple clients with the same common name to\n"
" concurrently connect.\n"