For performance reasons, Enigmail remembers the last decrypted message in memory and will not need gpg to decrypt it again. If that's not the case, then gpg does not require a passphrase for decryption.
-Patrick On 15.01.2019 17:35, Daniel Pecka wrote: > Patrick, as you couldd clearly see, enigmail message info says: > > Decrypted message > > Note: The message is encrypted for the following User ID's / Keys: > 0xA465836F77AD8DF8 (dpecka <[email protected]>), > 0xA7C056435C18F835 (dpecka <[email protected]>) > > and the colour of the bar is grey. > > dan > > > On 15/01/2019 17:23, Patrick Brunschwig wrote: >> >> >> On 15.01.2019 16:18, Daniel Pecka wrote: >>> On 15/01/2019 13:24, Patrick Brunschwig wrote: >>>> On 15.01.2019 11:30, Daniel Pecka wrote: >>>>> Hello folks, >>>>> >>>>> I have Enigmail version 2.0.8 (20181210-1200) and it seems to me, that >>>>> enigmail somehow remembers the passphrase for my gpg key(s) and doesn't >>>>> ask anymore when sending email (for subscribing) .. >>>> >>>> Enigmail doesn't remember any passphrase, nor would it ask for any >>>> passphrase. That's handled by gpg-agent. >>>> >>>>> I ofc googled and tried to -HUP gpg-agent which indeed works and when I >>>>> want to decrypt/sign something from cli using gpg2, pinetry asks for >>>>> passphrase but enigmail doesn't .. >>>>> >>>>> I'd like to set enigmail to ALWAYS ask for passphrase when sending, is >>>>> it possible ? >>>> >>>> gpg-agent _will_ remember the passphrase for a while (depending on your >>>> configuration between some minutes and a few hours). You can try to set >>>> max-cache-ttl to 10 (=10 seconds). I don't recommend setting it to 0, >>>> because Enigmail will always first attempt to encrypt and then do the >>>> actual encryption in a second step. >>>> >>> Hello Patrick, >>> >>> thanks for info ... you were right .. after delivering SIGHUP signal to >>> gpg-agent process it indeed asks again for passphrase when enigmail >>> attempts to use my key for signing but I don't how it works with >>> decrypting keys .. after -HUPing gpg-agent I can still see the content >>> of older encrypted emails without entering passphrase with enigmail info >>> below (example - I've substituted domains by xxxxx/yyyyy resp.) >>> >>> Decrypted message >>> >>> Note: The message is encrypted for the following User ID's / Keys: >>> 0xA465836F77AD8DF8 (dpecka <[email protected]>), >>> 0xA7C056435C18F835 (dpecka <[email protected]>) >>> >>> as I am writing this message now, just once I will hit send button, >>> enigmail will ask me for passphrase for signing but I can view before I >>> do so and before gpg-agent caches it the content of older encrypted >>> emails .. is this expected behaviour ? I use enigmail defaults >> >> >> You don't need a passphrase to read signed-only messages. The passphrase >> is only needed to create signed messages, and to read encrypted messages. >> >> -Patrick >> >> >> >> >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
