Daiki Ueno wrote:
In
4a8c5344.4060701__17863.5451746688$1250713354$gmane$...@dougbarton.us
Doug Barton do...@dougbarton.us wrote:
Today I mis-typed a passphrase for a symmetrically encrypted file and
was surprised to discover that gpg-agent had stored the bad passphrase
and would not let
On Tue, 18 Aug 2009 20:28, do...@dougbarton.us said:
Today I mis-typed a passphrase for a symmetrically encrypted file and
was surprised to discover that gpg-agent had stored the bad passphrase
and would not let me access the file. I have occasionally in the past
This is a new and probably
Werner Koch wrote:
On Tue, 18 Aug 2009 20:28, do...@dougbarton.us said:
Today I mis-typed a passphrase for a symmetrically encrypted file and
was surprised to discover that gpg-agent had stored the bad passphrase
and would not let me access the file. I have occasionally in the past
This
In
4a8c5344.4060701__17863.5451746688$1250713354$gmane$...@dougbarton.us
Doug Barton do...@dougbarton.us wrote:
Today I mis-typed a passphrase for a symmetrically encrypted file and
was surprised to discover that gpg-agent had stored the bad passphrase
and would not let me access the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I run gpg-agent with the ssh option in my .xsession file so that all
the child processes inherit the environment. This is needed mostly for
the ssh portion of course, since I could update the gpg part of the
agent stuff in .bashrc if I wanted to
