diff options
| author | Richard Levitte <levitte@openssl.org> | 2018-06-13 00:29:48 +0200 |
|---|---|---|
| committer | Richard Levitte <levitte@openssl.org> | 2018-06-13 10:27:03 +0200 |
| commit | 55c5c1b63a5f2497e26d734d597c40e4a36fe4af (patch) | |
| tree | 906165f4dd754993c6291dc00991c01ba40200eb | |
| parent | 0df65d82dbc41e8da00adb243de5918db532c8a6 (diff) | |
doc/man7/passphrase-encoding.pod: Make consistent
The man name didn't match the file name, and some places had
'password' instead of 'pass phrase'.
Fixes #6474
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/6476)
| -rw-r--r-- | doc/man7/passphrase-encoding.pod | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/man7/passphrase-encoding.pod b/doc/man7/passphrase-encoding.pod index d5c9d1e6f6..6810844526 100644 --- a/doc/man7/passphrase-encoding.pod +++ b/doc/man7/passphrase-encoding.pod @@ -4,7 +4,7 @@ =head1 NAME -password encoding +passphrase-encoding - How diverse parts of OpenSSL treat pass phrases character encoding =head1 DESCRIPTION @@ -61,11 +61,11 @@ OpenSSL still does this, to be able to read files produced with older versions. It should be noted that this approach isn't entirely fault free. -A passphrase encoded in ISO-8859-2 could very well have a sequence such as +A pass phrase encoded in ISO-8859-2 could very well have a sequence such as 0xC3 0xAF (which is the two characters "LATIN CAPITAL LETTER A WITH BREVE" and "LATIN CAPITAL LETTER Z WITH DOT ABOVE" in ISO-8859-2 encoding), but would be misinterpreted as the perfectly valid UTF-8 encoded code point U+00EF (LATIN -SMALL LETTER I WITH DIARESIS) I<if the passphrase doesn't contain anything that +SMALL LETTER I WITH DIARESIS) I<if the pass phrase doesn't contain anything that would be invalid UTF-8>. A pass phrase that contains this kind of byte sequence will give a different outcome in OpenSSL 1.1.0 and newer than in OpenSSL older than 1.1.0. @@ -133,7 +133,7 @@ following: =item 1. -Try the password that you have as it is in the character encoding of your +Try the pass phrase that you have as it is in the character encoding of your environment. It's possible that its byte sequence is exactly right. |