Accepted gnupg2 2.1.7-1 (source) into experimental
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 11 Aug 2015 20:05:38 -0400
Source: gnupg2
Binary: gnupg-agent scdaemon gpgsm gnupg2 gpgv2 dirmngr gnupg2-dbg
Architecture: source
Version: 2.1.7-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GnuPG Maintainers <pkg-gnupg-maint@lists.alioth.debian.org>
Changed-By: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Description:
dirmngr - server for managing certificate revocation lists
gnupg-agent - GNU privacy guard - cryptographic agent
gnupg2 - GNU privacy guard - a free PGP replacement (new v2.x)
gnupg2-dbg - debugging symbols for gnupg2
gpgsm - GNU privacy guard - S/MIME version
gpgv2 - GNU privacy guard - signature verification tool (new v2.x)
scdaemon - GNU privacy guard - smart card support
Changes:
gnupg2 (2.1.7-1) experimental; urgency=medium
.
* new upstream release
* block ptrace connections to gpg-agent
Checksums-Sha1:
9a8d63ab94724bbc0fdf24828e3ad09b3dc04837 2690 gnupg2_2.1.7-1.dsc
1a345804f34a2acd05c1555e40ddfa297f38438b 4918583 gnupg2_2.1.7.orig.tar.bz2
c4b836567b64c405ce0c1a072abcbee4ce767106 28532 gnupg2_2.1.7-1.debian.tar.bz2
Checksums-Sha256:
57f1b62e84fb7b1cf861fa230690906ca5d5eae913d84022b990fdd09c233892 2690 gnupg2_2.1.7-1.dsc
c18a3776d47fec98892d51d28b6574ef16bf0a25eabb0956231058aaf2e7846e 4918583 gnupg2_2.1.7.orig.tar.bz2
00ef37caabfb7a801d4189889516bebbaf54101fcd83cd8a3a09092dcbfb4d91 28532 gnupg2_2.1.7-1.debian.tar.bz2
Files:
e02399ceba5a897eea8ab28335b56bab 2690 utils optional gnupg2_2.1.7-1.dsc
ebdf92b15b8bcd8579b643c7f41a3238 4918583 utils optional gnupg2_2.1.7.orig.tar.bz2
fcd01f35b41fc9ea04ff717c06270ee0 28532 utils optional gnupg2_2.1.7-1.debian.tar.bz2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQJ8BAEBCgBmBQJVypsvXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQjk2OTEyODdBN0FEREUzNzU3RDkxMUVB
NTI0MDFCMTFCRkRGQTVDAAoJEKUkAbEb/fpc5RsP/0E0T37ADlinTDgJUOLj3GWg
yOHQInB92Zi5NUAzEHTGGug4yd8fWhKS9CmPc39crF638EyL4epdGqJ5FtUWaZyR
PcJmhI8pFczyHurb9ssGDlgb6aLp60Ru9lGHc/AC3jgWl9OvIIQ4HZNoLpUquzTL
Dj1iGzE2wZoT9MV2s+XVa5i8M/bpDTwFtNsHaBdRsPOCGtipbxk/3WmG640VGEQJ
dSsFsHG//LQwP0t+JLFhscGSekfTk2x16GSRUT+0zUlivIuekvI23EksP3Api1zq
dk1yQuvh8RQVakNkBODVl53mNU0mfQZX0R5RXgI0bJG9wDyi78yhDqhClvXthZue
32Yc9IpzyBgB/oV6g+Frv5+4JD+Jgo4K8f4s5NHkdZ5qYJ6GrpjpMEzZifdKuUcQ
M0izu8W37cPsD9JU/jifL67WnvAIpMJ50Kx2moPN6MhenbffNoZDoV2LX5zGDVtL
52E4l3D9nYqsPr3KSCF9Js2jlpet15YhhS4/02zdvnV+qm8FD7PTwE+DDS/TRVju
vzgK0kI0CPJIPzYSiV+jHwJh6NX7obdXVAZX83p3Iwy5mps9NxegYNi3NQhHp5FG
wQTkKHKwFqeamQfYhBs+Ozg3O05mRbjkvst49mlGS2mYxwtv6mupyvD472Na+14g
jaQ975XiHMhllSeSZjN1
=TYo5
-----END PGP SIGNATURE-----
Reply to: