Package: gnupg Version: 2.1.16-3 Followup-For: Bug #847552 Dear Maintainer,
I have the same problem. stracing gpg -d gives me a lot of this: "S PROGRESS need_entropy X 30 120"..., 1002) = 33 read(6, "S PROGRESS need_entropy X 120 12"..., 1002) = 34 read(6, "S PROGRESS need_entropy X 30 120"..., 1002) = 33 read(6, "S PROGRESS need_entropy X 120 12"..., 1002) = 34 read(6, "S PROGRESS need_entropy X 30 120"..., 1002) = 33 which led me to this patch: https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=4473db1ef24031ff4e26c9a9de95dbe898ed2b97 With the patch reverted, the 10 seconds delay is gone. Note that I have no idea about security implications of this revert, nor why it needs entropy when doing gpg -d. Cheers Jochen -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.8.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages gnupg depends on: ii gnupg-agent 2.1.16-3 ii libassuan0 2.4.3-2 ii libbz2-1.0 1.0.6-8 ii libc6 2.24-8 ii libgcrypt20 1.7.5-2 ii libgpg-error0 1.25-2 ii libksba8 1.3.5-2 ii libreadline7 7.0-1 ii libsqlite3-0 3.15.2-1 ii zlib1g 1:1.2.8.dfsg-4 Versions of packages gnupg recommends: ii dirmngr 2.1.16-3 pn gnupg-l10n <none> Versions of packages gnupg suggests: pn parcimonie <none> pn xloadimage <none> -- no debconf information
