Which release should we be using?

[Anthony Papillion]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 08/22/2011 07:01 AM, Werner Koch wrote:
> On Mon, 22 Aug 2011 10:29, papillion at gmail.com said:
> 
>> because I don't like having to use pinentry since it doesn't support cut
>> and paste. My questions are these:
> 
> That is on purpose.  If you have your passphrase on file for c+p you may
> as well use no passphrase at all.  gpg-agent caches your passphrase; set
> the caching time to whatever you l; this is far safer than to use c+p.

Hi Werner,

I'm not sure I can see how being able to cut and paste a passphrase is
in any way like not having a passphrase at all. My passphrases are
stored in a Keepass database that resides in a TrueCrypt container. It's
protected well. My actual key is protected by a 62 character passphrase
that I'd like to cut and paste into GPG. Considering all of that, I
think it's a bit extreme to say cutting and pasting a passphrase from
two heavily encrypted containers is such that you may as well not have a
passphrase at all.

Still, thanks for your input. I suppose I could always implement c+p in
my version of pinentry or I'll just stick with 1.4.x for a while.

Thanks!
Anthony
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJOUwaUAAoJEFMVikTZRCu/MEYP/36u1JOBc0OjeO7Ti+NDszII
ho2RPGzqnLhP0QiBsjvDNXdxCr4y8u7LWFhkHtcpKvdrmUwqminSvm2Fgv3Jxw6o
TX5q3hwmUT1oPiYwVXr4toGwnxgG1kS78WpFcMYfQiPf4L3igRslM5Ai/0PaE6K3
Zrpnmh4FtFq8i5CVnPR0S8RUEBKHibdWJY4yTPPj9YrXThlDtNK5m05bWjbylwGT
NOZReM4xLoOzKsnsBnC71lqyDoyGN67dYiuIZXNiVmW+8CTTtxWtyNAndzRI48hb
NMBEL4C1Bmpm6hWXepj+3g7iXRSxCe07TRBHxJRbxRYXPeWc4Yr5BloVtj/pJfIE
IMgohU/bY7XMc31/Q5RPWrSa/JGCz/itv6XW93fkkhE3hdp2gzaZJM6UufCz2Vrx
E9EG4OJZTiYQDomEagoEywsjI9vKwDLr7qpiekYsf2vKctE+0cj8xYDUQZ4f1vK0
WuSf5KGSU5EgjAfFblZoq/ck3nagw+B/VcNzYlaJyyroOTy/t7p+bvmR85oiqg5J
UZr7shMIIy8D+9A66/rNT0lUzYLv7lpv6lyikQoY65eO6gu3nqFA8pqO09CD8lHE
hcHD0/EcecCcZmAQ/Sic71jVzAxq7JKbA38RntWvQoK4BVPY3LDhBBMW97WHAT3k
XQve2O8L1vegnGfxatE1
=nsTK
-----END PGP SIGNATURE-----