Lines Matching refs:encoding
3 =encoding utf8
7 passphrase-encoding
8 - How diverse parts of OpenSSL treat pass phrases character encoding
25 Using the wrong encoding is expected to cause a decryption failure.
29 PKCS#12 is a bit different regarding pass phrase encoding.
49 encoding of the characters, which it stores as a BMPString.
53 for other character sets, such as any ISO-8859-X encoding other than
66 and "LATIN CAPITAL LETTER Z WITH DOT ABOVE" in ISO-8859-2 encoding), but would
84 other pass phrase encoding may give undefined results.
85 This API relies on the application to ensure UTF-8 encoding, and doesn't check
92 but that it may have been encoded in a different character encoding than the
95 encoding was ISO-8859-1 (i.e. "naïve" resulting in the byte sequence 0x6E 0x61
96 0xEF 0x76 0x65), and you're now in an environment where your default encoding
99 Whenever it's mentioned that you should use a certain character encoding, it
101 mentioned encoding when you type in your pass phrase, or use some suitable tool
102 to convert your pass phrase from your default encoding to the target encoding.
109 character encoding discussion irrelevant; in such cases, simply use the same
125 encoding was used for the encryption pass phrase, make sure to use the same
126 encoding again.
128 For opening pass phrase protected objects where the character encoding that was
136 Try the pass phrase that you have as it is in the character encoding of your
158 erroneous/non-compliant encoding used by OpenSSL older than 1.1.0)
