GPG Pin entry / Passphrase on Enigmail with IceDove / Thunderbird

[Max]

I appreciate this is probably not a Qubes specific question but given that I couldn't find the answer on other threads and I suspect others on this distribution list would be using a similar version of software I wanted to check if this was a known issue/feature.

I am currently unable to paste the passphrase into the pin entry in Enigmail when attempting to decrypt my messages. This worked a few weeks ago. Also, once I manually type in the key, the password is not cached at all meaning I have to type it in repeatedly for every message. Is there a way to change this behaviour?

I am using Debian 8 on Qubes 3.2 with Enigmail 1.8.2 downloaded from the Debian software packages as opposed to the Thunderbird / Icedove add ons.

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

There was a recent thread on this:

https://groups.google.com/d/topic/qubes-users/8g-WwvOw_ck/discussion

Short answer:

"You may experience trouble when attempting to use a PGP key with a
passphrase along with Split-GPG and Enigmail. If you do, you may need
to remove the passphrase from your (sub)key(s) in order to get
Split-GPG working correctly. As mentioned above, we do not believe PGP
key passphrases to be significant from a security perspective."

From: https://www.qubes-os.org/doc/split-gpg/

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYiv74AAoJENtN07w5UDAwFdYP/12GYp+MxoM2BLiQHyEFxux+
BdgSnHpqUrNozM0FA8q/GUmeqaU/BZadnq34t7CU+beCuweQqwEjHdKA94YRI0az
+/u9IP3Xd+S6fhmZy9uKWpHQehVkH4YsYbIi08oYUpKf5LFzFLznTIKUC/VE/52b
WWMUYhzawhaqefH1LgFllC6SAswI3BRZFdIDRRhMVCMLgnQcK/oyrvfOfloOMl4/
t51aHfZxsmuW3TE53rOkSJPfWMJpwDuokd+80KFw0tshMAjl5snI1q9p6HL4NVdd
2yy21ST0wvbMFGUm/5eRW3yBfuuNWpQE3FTbgQf8jLDGePoKzin/WkKnJtGXNbJL
Hp6lIn1SUMm0S9WoHweL4nqH3u4gTPUwD2xwgEVX6YtsEHJ9rkPWs94lDbE+RJAr
2OXus9zmZ85tiqZJafUHLrDANko6cK72mqzTiM7vS4RX5sac6qAMZOKO2o0i6fFC
++PFmI7+Ll50qrNEMYTb9EDWfhEocWr3+luRJU0yYrv0Q6J9GeKVrKIYWN2m24Du
YXb1mupDrwuG36KHWTmj2rADe20zECD72VjZ6ZxoYDIwrsP1T2TLI+yJeMclp1Nt
ImNxMK5kSt2j5wdxutIfl1tlBZZGiivw7nKw1dTZ5ZbsvQib44xvGh1/ExHeEgka
sjDmundAm8K0Avt5DKmn
=Hvgh
-----END PGP SIGNATURE-----