diff options
| author | FdaSilvaYY <fdasilvayy@gmail.com> | 2016-06-28 22:51:51 +0200 |
|---|---|---|
| committer | Rich Salz <rsalz@openssl.org> | 2016-06-29 09:56:39 -0400 |
| commit | 6b4a77f56e14c002ce3cf960f622682be3b8424b (patch) | |
| tree | 5fbdcaa46159cf3183f17e913f50b46c94e80080 /doc | |
| parent | 0485d5406a3b76dd02e73c1c7dcabebe64f9f8a2 (diff) | |
Whitespace cleanup in apps
Reviewed-by: Andy Polyakov <appro@openssl.org>
Reviewed-by: Kurt Roeckx <kurt@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/1264)
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/crypto/OPENSSL_malloc.pod | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/crypto/OPENSSL_malloc.pod b/doc/crypto/OPENSSL_malloc.pod index cd89897b60..9760135ee9 100644 --- a/doc/crypto/OPENSSL_malloc.pod +++ b/doc/crypto/OPENSSL_malloc.pod @@ -103,7 +103,7 @@ 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 that sensitive tail bytes will survive zeroization because the block of -zeros will be compressed. If the storage controller uses wear levelling, +zeros will be compressed. If the storage controller uses wear leveling, then the old sensitive data will not be overwritten; rather, a block of 0's will be written at a new physical location. |