security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-02 22:46:30 +02:00
Code Activity

Fix explanation of commit e175152ef7.

Browse source 
--
This commit is contained in:
Werner Koch 2017-02-01 08:18:44 +01:00
parent 8ddc9268f6
commit f518196ca6
No known key found for this signature in database
GPG key ID: E3FDFF218E45B72B
2 changed files with 6 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
agent/cache.c
View file

@ -485,10 +485,12 @@ agent_store_cache_hit (const char *key)
*
* Background: xtrystrdup uses gcry_strdup which may use the secure
* memory allocator of Libgcrypt. That allocator takes locks and
* since version 1.14 libgpg-error is nPth aware and thus talking a
* since version 1.14 libgpg-error is nPth aware and thus taking a
* lock may now lead to thread switch. Note that this only happens
* when secure memory is allocated, the standard allocator uses
* malloc which is not nPth aware.
* when secure memory is _allocated_ (the standard allocator uses
* malloc which is not nPth aware) but not when calling _xfree_
* because gcry_free needs to check whether the pointer is in secure
* memory and thus needs to take a lock.
*/
new = key ? xtrystrdup (key) : NULL;