Closed leonardo0014 closed 2 weeks ago
I assume the error is a Windows CP-1252 encoding of the friendly name during creation, instead of the required BMPSTRING (2byte unicode). Just a wild guess. There is not much XCA can do to correct this automatically.
Thanks for the quick reply. So it's a problem with the source of the PKCS12 container. Then I have to tell the certificate issuer that they're using more "non-Windows" encoding. Let's see what they'll answer, which I can already guess based on the CPS.
German umlauts are not imported correctly or are not corrected. My example Certificates with umlauts that have an error in the friendlyName will not be corrected. Instead of "BJÖRN" comes "BJ�RN"
Currently only tested with Debian Stable XCA Package Any idea what could be causing this?
XCA
PKCS#12 Container
Please ignore the fact that the old encryptions for the pkcs#12 Container are still used. The example is a bit older ;-)