Hello, Accented letters are indispensable in many languages other than English. In practice, this prevents some users from entering correctly spelled identity information, for example a French region name, a Luxembourg locality, or an Italian organization name. It is worth recalling that the X.509 standard, as defined in RFC 5280, section 4.1.2.4 (DirectoryString), explicitly provides for the use of UTF8String, allowing Unicode characters to be used in certificate identity fields (Organization, Locality, etc.): https://datatracker.ietf.org/doc/html/rfc5280#section-4.1.2.4 By contrast, most server management interfaces and modern ACME tools support this capability and accept accented characters in compliance with the standard. It might, therefore, be useful to align the validation with this UTF-8 capability, to avoid any normative inconsistency from a user perspective. Thank you for your work. Kind regards,
As ispconfig is nothing more than a shell around a collection of packages it can only be done if ALL packages (to which it applies) are fully compliend. On ALL supported OS's.
Hello, Thank you for your feedback. I would nonetheless like to point out a very concrete issue. The current validation message states: This list therefore already explicitly allows certain non-ASCII UTF-8 characters, but in a way limited to a specifically German linguistic particularity. This shows that the restriction does not stem from the X.509 standard nor from the underlying tools, but rather from a validation choice at the interface level. In this context, aligning the validation with the UTF8String type provided for in RFC 5280 would help avoid an arbitrary regional restriction and ensure better normative compliance for all languages. Kind regards,
Agreed I'm no programmer and didn't dive into things. I simply outlined what ispconfig is and what could possibly hold back the requested change.
