summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>2016-12-07 18:55:06 +0100
committerWerner Koch <wk@gnupg.org>2016-12-07 18:55:06 +0100
commit677ddf5bbd9c172a72607c7d5d7006907071c2cf (patch)
tree62f341e9702cf38fcbcb0025bdb6ce8238eedc60 /NEWS
parent95bac312644ad45e486c94c2efd25d0748b9a20b (diff)
downloadlibgcrypt-677ddf5bbd9c172a72607c7d5d7006907071c2cf.tar.gz
doc: Update NEWS.
--
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS8
1 files changed, 8 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 0aaf8630..722172a3 100644
--- a/NEWS
+++ b/NEWS
@@ -15,6 +15,14 @@ Noteworthy changes in version 1.8.0 (unreleased) [C21/A1/R_]
blocking read of /dev/random. This allows other nPth threads to
run while Libgcrypt is gathering entropy.
+ - When secure memory is requested by the MPI functions or by
+ gcry_xmalloc_secure, they do not anymore lead to a fatal error if
+ the secure memory pool is used up. Instead new pools are
+ allocated as needed. These new pools are not protected against
+ being swapped out (mlock can't be used). However, these days
+ this is considered a minor issue and can easily be mitigated by
+ using encrypted swap space.
+
* Interface changes relative to the 1.6.0 release:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~