• https://www.gnupg.org/ftp/gcrypt/libgcrypt/ (Download)
• https://mirrors.dotsrc.org/gcrypt/libgcrypt/ (Download)
• ftp://ftp.gnupg.org/gcrypt/libgcrypt/ (Download)

• (2019-09-08) Updated to version: libgcrypt-1.8.5
• (2018-12-03) Updated to version: libgcrypt-1.8.4
• (2018-06-14) Updated to version: libgcrypt-1.8.3
• (2017-12-14) Updated to version: libgcrypt-1.8.2
• (2017-08-28) Updated to version: libgcrypt-1.8.1
• (2017-07-20) Updated to version: libgcrypt-1.8.0
• (2017-06-30) Updated to version: libgcrypt-1.7.8
• (2017-06-05) Updated to version: libgcrypt-1.7.7
• (2017-01-19) Updated to version: libgcrypt-1.7.6
• (2016-12-16) Updated to version: libgcrypt-1.7.5

Log message:
- SECURITY mitigation against an ECDSA timing attack [CVE-2019-13627].
- Improve ECDSA unblinding.

Log message:
SECURITY update to libgcrypt-1.8.5.
- Add mitigation against an ECDSA timing attack [CVE-2019-13627]

Log message:
replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes

Log message:
use arc4random_buf(3) in libgcrypt instead of /dev/random
this issue came to the light after using an unveil(2)'d chrome
inside a GNOME environment where it was trying to use the keyring
which was relying on libgcrypt
ok ajacoutot@

Log message:
Update to libgcrypt-1.8.4.

Log message:
SECURITY update to libgcrypt-1.8.3 (CVE-2018-0495).

Log message:
SECURITY update to libgcrypt-1.8.3 (CVE-2018-0495).

Log message:
Tweak the HOMEPAGE of gnupg.org ports
- move to https
- use the per-project canonical homepage (reachable thru the main
- homepage; pinentry doesn't seem to have such homepage)
ok pea@ ajacoutot@

Log message:
Update to libgcrypt-1.8.2.

Log message:
Merge upstream fix for:
- CVE-2017-0379 - side-channel attack on Curve25519

Log message:
SECURITY update to libgcrypt-1.8.1.
- CVE-2017-0379 - side-channel attack on Curve25519

Log message:
Update to libgcrypt-1.8.0.

Log message:
SECURITY update to libgcrypt-1.7.8.
[CVE-2017-7526]
- See https://eprint.iacr.org/2017/627 for details.

Log message:
SECURITY update to libgcrypt-1.7.8.
[CVE-2017-7526]
- See https://eprint.iacr.org/2017/627 for details.

Log message:
Update to libgcrypt-1.7.7.

Log message:
Update to libgcrypt-1.7.6.

Log message:
Update to libgcrypt-1.7.5.

Log message:
Update to libgcrypt-1.7.4.

Log message:
rename MASTER_SITES_GNUPG to MASTER_SITE_GNUPG, like all the others

Log message:
Fix for CVE-2016-6313.

Log message:
Fix for CVE-2016-6313.

Log message:
SECURITY update to libgcrypt-1.7.3.
CVE-2016-6313

Log message:
Update to libgcrypt-1.7.2.
ok sthen@ before lock

Log message:
Update to libgcrypt-1.7.1.

Log message:
Committed upstream.

Log message:
Re-add the error message that motivated those patches
crc-intel-pclmul.c:369: Error: no such instruction: `pextrd $1,%xmm0,(%rdi)'

Log message:
Drop use of pclmul/SSE4.1 for CRC, and the use of clang while here
While this bring a nice speed improvement over libgcrypt-1.6.5, it
requires newer gcc or clang.  Since libgcrypt is a requirement for
tons of ports, using clang here means that you end up building two huge
compilers before building anything useful.
pclmul alone is supported by base gcc and is still used for GCM.
ok ajacoutot@ (maintainer)

Log message:
Only use clang for i386 and amd64.

Log message:
Update to libgcrypt-1.7.0.

Log message:
replace the gettext module with conventional dependencies; ok ajacoutot@

Log message:
garbage collect CONFIGURE_SHARED

Log message:
CVE-2015-7511 libgcrypt: side-channel attack on ECDH with Weierstrass curves
ok aja@

Log message:
Update to libgcrypt-1.6.5 to fix CVE-2015-7511.
prodded by Sevan Janiyan
ok sthen@

Log message:
Update to libgcrypt-1.6.4.

Log message:
SECURITY update to libgcrypt-1.6.3.
CVE-2014-3591, CVE-2015-0837
prodded by "Corey"
ok sthen@

Log message:
- remove unneeded patches, all the random devices have been providing the same
output for a while now.
- fix a few license markers while here

Log message:
Better HOMEPAGE.

Log message:
new depends

Log message:
Maintainance update to libgcrypt-1.4.6.

Log message:
Minor update to libgcrypt-1.4.5.

Log message:
- use /dev/arandom as entropy source
ok jasper@

Log message:
- update to libgcrypt-1.4.4
works for pea@ on amd64

Log message:
- remove bogus BUILD_DEPENDS on transfig (fig2dev is never called)
This should fix the dependency loop on cups reported by naddy@

Log message:
gcc-3.3.5 workaround: g++ doesn't understand attributes on enums.
Bump PKGNAME.
ok naddy@ espie@

Log message:
Update libgcrypt to 1.4.3.
ok naddy@ ajacoutot@

Log message:
On hppa, udiv_qrnnd is only provided as asm, which has been disabled
with a "--disable-asm" configure flag. Remove this flag for hppa.
Didn't build there before, and other arch are unaffected, so no bump.
ok mbalmer

Log message:
update to 1.2.4
from Mikolaj Kucharski

Log message:
Remove surrounding quotes in NO_REGRESS/COMMENT*/PERMIT_*
From Darrin Chandler

Log message:
more base64 checksums

Log message:
give up MAINTAINER, I don't use these anymore

Log message:
fix build on sparc
noticed and tested by pval

Log message:
SHARED_LIBS
USE_LIBTOOL where applicable

Log message:
typo and wording fixes; approved by pval
ok mbalmer@ "that diff was fun to read"

Log message:
Now that @info transparently picks up all .info-* files, don't go through
extra steps to rebuild with --no-split.

Log message:
SIZE

Log message:
new plists.
gnutls depends on lzo.

Log message:
fix build on alpha

Log message:
fix serpent on sparc64

Log message:
ups, that was wrong

Log message:
don't use /dev/random

Log message:
update to libgcrypt 1.2.0
take maintainer, ok Jim Geovedi

Log message:
remove workaround for gcc2.95/sparc64 optimizer bug: sha1.c compiles fine now

Log message:
@dirrm shared directories

Log message:
libgcrypt-config --libs should report -pthread as well.

Log message:
- use arandom for random devices
- bump PKGNAME
--
Based on patch from MAINTAINER