diff options
| author | Ivan Filenko <ivan.filenko@protonmail.com> | 2018-02-25 16:49:27 +0300 |
|---|---|---|
| committer | Dr. Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com> | 2018-03-01 20:15:21 +0100 |
| commit | c1190c32c42b1e3ce35ea2ea8f214f46f336c5ed (patch) | |
| tree | b9e6656d4f7d018fc97340f968c72a3aaf316a7e /doc | |
| parent | b3f9b401ab6284e6bbde59dde06736f681f70a9d (diff) | |
Fix typo in ASN1_STRING_length doc
CLA: trivial
Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
(Merged from https://github.com/openssl/openssl/pull/5458)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/crypto/ASN1_STRING_length.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/crypto/ASN1_STRING_length.pod b/doc/crypto/ASN1_STRING_length.pod index f651e4f2ae..4ea6e8c226 100644 --- a/doc/crypto/ASN1_STRING_length.pod +++ b/doc/crypto/ASN1_STRING_length.pod @@ -66,8 +66,8 @@ utility functions should be used instead. In general it cannot be assumed that the data returned by ASN1_STRING_data() is null terminated or does not contain embedded nulls. The actual format of the data will depend on the actual string type itself: for example -for and IA5String the data will be ASCII, for a BMPString two bytes per -character in big endian format, UTF8String will be in UTF8 format. +for an IA5String the data will be ASCII, for a BMPString two bytes per +character in big endian format, and for an UTF8String it will be in UTF8 format. Similar care should be take to ensure the data is in the correct format when calling ASN1_STRING_set(). |