Re: [Mutt] #580: mutt stores PGP passphrase insecurely
- To: md@xxxxxxxx, arturcz@xxxxxxx, brendan@xxxxxxxxxx, brian@xxxxxxxxxxxxx, invalid@xxxxxxxxxxxxxx, ttakah@xxxxxxxxxxxxxxxxx, roessler@xxxxxxxxxxxxxxxxxx, wk@xxxxxxxxx, antonio@xxxxxxxx, paul@xxxxxxxxxxxxxxx, pdmef@xxxxxxx, petr.pisar@xxxxxxxx
- Subject: Re: [Mutt] #580: mutt stores PGP passphrase insecurely
- From: Mutt <fleas@xxxxxxxx>
- Date: Mon, 27 Jul 2009 17:13:38 -0000
- Auto-submitted: auto-generated
- Cc: mutt-dev@xxxxxxxx, 96144@xxxxxxxxxxxxxxx
- In-reply-to: <058.5fa77f122be3996dabecb666b4de6ee9@xxxxxxxx>
- Mail-followup-to: fleas@xxxxxxxx
- References: <058.5fa77f122be3996dabecb666b4de6ee9@xxxxxxxx>
- Reply-to: fleas@xxxxxxxx
#580: mutt stores PGP passphrase insecurely
-----------------------------------------+----------------------------------
Reporter: Marco d'Itri <md@xxxxxxxx> | Owner: mutt-dev
Type: defect | Status: reopened
Priority: trivial | Milestone:
Component: crypto | Version: 1.5.19
Resolution: | Keywords:
-----------------------------------------+----------------------------------
Comment(by Werner Koch):
{{{
On Mon, 27 Jul 2009 17:42, fleas@xxxxxxxx said:
Unless you use "set crypt_use_gpgme" in which case gpg-agent takes care
of everything.
FWIW, the latest gpgme release 1.2.0 allows direct access to gpg-agent
and thus you can make use of the gpg-agent's passphrase caching feature.
Shalom-Salam,
Werner
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/580#comment:>
Mutt <http://www.mutt.org/>
The Mutt mail user agent