Enigmail und GnuPG

Hallo zusammen,

ich habe folgende Konstellation:

Debian 9 (testing), Kernel 4.2 amd64, Cinnamon 2.6.13
Thunderbird 38.3 + Enigmail 1.8.2
GnuPG 1.4.19, Seahorse 3.18.0, pinentry-gtk 0.9.6

Ich habe meinen GPG-Schlüssel im »Key Management« von Enigmail aus einer Sicherungsdatei importiert.

Problem: Jedes Mal, wenn der Schlüssel gebraucht wird, also beim Signieren und Entschlüsseln, braucht es ca. 30 Sekunden, bevor die Abfrage der Passphrase erscheint. Auszug aus dem (»geschwärzten«) Enigmail-Log

Code:

---

2015-11-09 13:41:32.290 [DEBUG] enigmail.js: detected GnuPG version '2.0.28'
2015-11-09 13:41:32.291 [DEBUG] enigmail.js: Enigmail.setAgentPath: gpgconf found: yes
2015-11-09 13:41:32.291 [DEBUG] enigmail.js: detectGpgAgent
2015-11-09 13:41:32.291 [DEBUG] enigmail.js: detectGpgAgent: GPG_AGENT_INFO variable available
2015-11-09 13:41:32.291 [DEBUG] enigmail.js: detectGpgAgent: GPG_AGENT_INFO='/home/florian/.gnupg/S.gpg-agent:3382:1'
2015-11-09 13:41:32.291 [DEBUG] enigmail.js: Setting useAgent to true for gpg2 >= 2.0.16
2015-11-09 13:41:32.291 [DEBUG] enigmailCommon.jsm: stillActive:
2015-11-09 13:41:32.291 [DEBUG] enigmail.js: Enigmail.initialize: END
2015-11-09 13:41:32.291 [DEBUG] enigmailCommon.jsm: getService: 1.8.2
2015-11-09 13:41:32.292 [DEBUG] enigmailCommon.jsm: getVersion
2015-11-09 13:41:32.292 [DEBUG] enigmailCommon.jsm: installed version: 1.8.2
2015-11-09 13:41:32.292 [DEBUG] mimeDecrypt.js: onStartRequest
2015-11-09 13:41:32.292 [DEBUG] mimeDecrypt.js: onStartRequest: uri='imap://[…]'
2015-11-09 13:41:32.292 [DEBUG] mimeVerify.jsm: setMsgWindow: imap-message://[…]
2015-11-09 13:41:32.295 [DEBUG] mimeVerify.jsm: onStartRequest
2015-11-09 13:41:32.295 [DEBUG] enigmailCommon.jsm: decryptMessageStart: verifyOnly=false
2015-11-09 13:41:32.296 enigmailCommon.jsm: execStart: command = /usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2 --max-output 188800 --decrypt, needPassphrase=true, domWindow=[object ChromeWindow], listener=[object Object]
2015-11-09 13:41:32.296 [DEBUG] enigmail.js: Setting useAgent to true for gpg2 >= 2.0.16
2015-11-09 13:41:32.296 [DEBUG] enigmailCommon.jsm: getPassphrase:
2015-11-09 13:41:32.296 [DEBUG] enigmail.js: Setting useAgent to true for gpg2 >= 2.0.16
2015-11-09 13:41:32.296 [CONSOLE] enigmail> /usr/bin/gpg2 --charset utf-8 --display-charset utf-8 --batch --no-tty --status-fd 2 --max-output 188800 --decrypt --use-agent
2015-11-09 13:41:32.300 [DEBUG]  enigmail> DONE
2015-11-09 13:41:32.309 [DEBUG] enigmail.js: Setting useAgent to true for gpg2 >= 2.0.16
2015-11-09 13:42:09.912 [DEBUG] enigmailCommon.jsm: decryptMessageEnd: uiFlags=8, verifyOnly=false, noOutput=false
2015-11-09 13:42:09.912 [DEBUG] enigmailCommon.jsm: decryptMessageEnd: stderrStr=
[GNUPG:] ENC_TO […] 1 0
[GNUPG:] USERID_HINT […]
[GNUPG:] NEED_PASSPHRASE […] […] 1 0
[GNUPG:] GOOD_PASSPHRASE
[GNUPG:] PROGRESS need_entropy X 8 16
[GNUPG:] PROGRESS need_entropy X 16 16
gpg: encrypted with 4096-bit RSA key, ID […], created […]
      "[…]"
[GNUPG:] BEGIN_DECRYPTION
[GNUPG:] DECRYPTION_INFO 2 9
[GNUPG:] PLAINTEXT […] […]
[GNUPG:] PLAINTEXT_LENGTH […]
[GNUPG:] NEWSIG
gpg: Signature made […]  using RSA key ID […]
[GNUPG:] SIG_ID […]
[GNUPG:] GOODSIG […]
gpg: Good signature from "[…]" [ultimate]
gpg:                aka "[…]" [ultimate]
[GNUPG:] VALIDSIG […]
[GNUPG:] TRUST_ULTIMATE
[GNUPG:] DECRYPTION_OKAY
[GNUPG:] GOODMDC
[GNUPG:] END_DECRYPTION

2015-11-09 13:42:09.912 [DEBUG] enigmailCommon.jsm: parseErrorOutput: status message:

---

Irgendwelche Ideen?
Besten Dank!
Florian