Lines Matching full:encoded
153 This means that for an object that was encrypted using a pass phrase encoded in
154 \&\s-1ISO\-8859\-1,\s0 that object needs to be decrypted using a pass phrase encoded in
160 The standard stipulates that the pass phrase shall be encoded as an \s-1ASN.1\s0
162 encoded in big endian (\s-1UCS\-2 BE\s0).
166 Treats the received pass phrase as \s-1UTF\-8\s0 encoded and tries to re-encode it to
171 Assumes that the pass phrase is encoded in \s-1ASCII\s0 or \s-1ISO\-8859\-1\s0 and
186 A pass phrase encoded in \s-1ISO\-8859\-2\s0 could very well have a sequence such as
189 be misinterpreted as the perfectly valid \s-1UTF\-8\s0 encoded code point U+00EF (\s-1LATIN
200 On the same accord, anything encoded in \s-1UTF\-8\s0 that was given to OpenSSL older
206 This \s-1API\s0 stipulates that pass phrases should be \s-1UTF\-8\s0 encoded, and that any
214 but that it may have been encoded in a different character encoding than the
236 encoded using \s-1UTF\-8.\s0
265 This also takes care of the case when a \s-1UTF\-8\s0 encoded string was used with
267 (for example, \f(CW\*(C`i\*:\*(C'\fR, which is 0xC3 0xAF when encoded in \s-1UTF\-8,\s0 would becom…
268 0x83 0xC2 0xAF when re-encoded in the nai\*:ve manner.