Lines Matching full:encoding
133 .IX Title "PASSPHRASE-ENCODING 7ossl"
134 .TH PASSPHRASE-ENCODING 7ossl "2023-09-19" "3.0.11" "OpenSSL"
140 passphrase\-encoding
141 \&\- How diverse parts of OpenSSL treat pass phrases character encoding
156 Using the wrong encoding is expected to cause a decryption failure.
159 PKCS#12 is a bit different regarding pass phrase encoding.
173 encoding of the characters, which it stores as a BMPString.
177 for other character sets, such as any \s-1ISO\-8859\-X\s0 encoding other than
188 and \*(L"\s-1LATIN CAPITAL LETTER Z WITH DOT ABOVE\*(R"\s0 in \s-1ISO\-8859\-2\s0 encoding), but wo…
207 other pass phrase encoding may give undefined results.
208 This \s-1API\s0 relies on the application to ensure \s-1UTF\-8\s0 encoding, and doesn't check
214 but that it may have been encoded in a different character encoding than the
217 encoding was \s-1ISO\-8859\-1\s0 (i.e. \*(L"nai\*:ve\*(R" resulting in the byte sequence 0x6E 0x61
218 0xEF 0x76 0x65), and you're now in an environment where your default encoding
221 Whenever it's mentioned that you should use a certain character encoding, it
223 mentioned encoding when you type in your pass phrase, or use some suitable tool
224 to convert your pass phrase from your default encoding to the target encoding.
231 character encoding discussion irrelevant; in such cases, simply use the same
245 encoding was used for the encryption pass phrase, make sure to use the same
246 encoding again.
248 For opening pass phrase protected objects where the character encoding that was
252 Try the pass phrase that you have as it is in the character encoding of your
270 erroneous/non\-compliant encoding used by OpenSSL older than 1.1.0)