Lines Matching refs:that

21 and stick to that throughout the lifetime of affected objects.
22 This means that for an object that was encrypted using a pass phrase encoded in
23 ISO-8859-1, that object needs to be decrypted using a pass phrase encoded in
30 The standard stipulates that the pass phrase shall be encoded as an ASN.1
42 to U+FFFF, but becomes an expansion for any other character), or failing that,
47 Assumes that the pass phrase is encoded in ASCII or ISO-8859-1 and
51 Note that since there is no check of your locale, this may produce UCS-2 /
52 UTF-16 characters that do not correspond to the original pass phrase characters
59 OpenSSL versions older than 1.1.0 do variant 2 only, and that is the reason why
62 It should be noted that this approach isn't entirely fault free.
68 SMALL LETTER I WITH DIAERESIS) I<if the pass phrase doesn't contain anything that
70 A pass phrase that contains this kind of byte sequence will give a different
76 On the same accord, anything encoded in UTF-8 that was given to OpenSSL older
83 This API stipulates that pass phrases should be UTF-8 encoded, and that any
86 that this is the case, so what it gets, it will also pass to the underlying
91 This section assumes that you know what pass phrase was used for encryption,
92 but that it may have been encoded in a different character encoding than the
99 Whenever it's mentioned that you should use a certain character encoding, it
100 should be understood that you either change the input method to use the
104 Also note that the sub-sections below discuss human readable pass phrases.
108 sequence of bytes from F</dev/urandom> that's been saved away), which makes any
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
138 It's possible that its byte sequence is exactly right.
143 Specifically with PKCS#12, this should open up any object that was created