Page Menu
Home
GnuPG
Search
Configure Global Search
Log In
Create Task
Maniphest
T4234
Libgcrypt 1.8.4 release info
Closed, Resolved
Public
Actions
Edit Task
Edit Related Tasks...
Create Subtask
Edit Parent Tasks
Edit Subtasks
Merge Duplicates In
Close As Duplicate
Edit Related Objects...
Edit Commits
Edit Mocks
Edit Revisions
Subscribe
Mute Notifications
Award Token
Assigned To
•
werner
Authored By
•
werner
Oct 26 2018, 6:39 PM
2018-10-26 18:39:29 (UTC+2)
Tags
Release Info
libgcrypt
(Backlog)
Subscribers
•
werner
Description
NEWS:
Bug fixes:
Fix infinite loop due to applications using fork the wrong way. [
T3491
]
Fix possible leak of a few bits of secret primes to pageable memory. [
T3848
]
Fix possible hang in the RNG (1.8.3 only). [
T4034
]
Several minor fixes. [
T4102
,
T4208
,
T4209
,
T4210
,
T4211
,
T4212
]
Performance:
On Linux always make use of getrandom if possible and then use its /dev/urandom behaviour. [
T3894
]
Details
Version
1.8.4
Related Objects
Mentions
Mentioned Here
T3491: FIPS-enabled libgcrypt traps gnome-keyring daemon in an infinite loop
T3848: Use of secure memory when generating secret primes in libgcrypt
T3894: re-evaluate default randomness choices during key generation on GNU/Linux platforms
T4034: libgcrypt: Fix for lock behavior broken in 1.8.3
T4102: libgcrypt: yat2m does not respect SOURCE_DATE_EPOCH, patch included
T4208: Copy & paste error in libgcrypt ecc-curves.c
T4209: Potential memory leak in _gcry_ecc_eddsa_verify
T4210: Potential memory leak in ecc_encrypt_raw
T4211: Potential memory leak in _gcry_secmem_malloc_internal
T4212: Uninitialized use of l1 variable in _gcry_sexp_vextract_param
Event Timeline
•
werner
created this task.
Oct 26 2018, 6:39 PM
2018-10-26 18:39:29 (UTC+2)
•
werner
renamed this task from
Ligcrypt 1.8.4 release info
to
Libcrypt 1.8.4 release info
.
Oct 26 2018, 8:01 PM
2018-10-26 20:01:21 (UTC+2)
•
werner
renamed this task from
Libcrypt 1.8.4 release info
to
Libgcrypt 1.8.4 release info
.
•
werner
closed this task as
Resolved
.
•
werner
claimed this task.
•
werner
updated the task description.
(Show Details)
Log In to Comment