]> git.ipfire.org Git - thirdparty/openssl.git/commitdiff
Fix typo in OPENSSL_malloc.pod
authorNan Xiao <nan@chinadtrace.org>
Tue, 8 Dec 2020 04:35:31 +0000 (12:35 +0800)
committerRichard Levitte <levitte@openssl.org>
Wed, 9 Dec 2020 12:36:55 +0000 (13:36 +0100)
CLA: trivial

Reviewed-by: Tomas Mraz <tmraz@fedoraproject.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/13632)

(cherry picked from commit 74c8dd1c516c7017477a205fd1f5f975cfa86722)

doc/man3/OPENSSL_malloc.pod

index c60e038309a1dbcef932ddabe02c8a9a8805e60b..9834a8f13147db8cf89c6dc354c5c1fdfda13a07 100644 (file)
@@ -104,7 +104,7 @@ before ultimately calling OPENSSL_free().
 
 OPENSSL_cleanse() fills B<ptr> of size B<len> with a string of 0's.
 Use OPENSSL_cleanse() with care if the memory is a mapping of a file.
-If the storage controller uses write compression, then its possible
+If the storage controller uses write compression, then it's possible
 that sensitive tail bytes will survive zeroization because the block of
 zeros will be compressed. If the storage controller uses wear leveling,
 then the old sensitive data will not be overwritten; rather, a block of