Thanks for the detailed reply.
Since --s2k-count will just affect the encryption of my private key, I'll go
ahead and give myself a half second delay.
sending passphrase-encrypted messages (which also have a s2k-count)
By this you mean symmetrically-encrypted messages, with the -c flag? So I
On Mon, 4 Jul 2011 05:01, ds...@jabberwocky.com said:
figures out how many iterations it can do in 1/10 of a second (which
always results in a value higher than 65536 these days), and uses
that. I believe that the newer GPG (2.x) has some support for this
design, but I don't recall offhand
Thanks.
There's no way to change the cipher used for encrypting the private key itself
(CAST5 I believe)?
(Not that I would, as I'm sure the default is more than good enough for my
needs.)
Also, if I understand correctly, someone trying to brute-force the key would
need to guess my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi
On Sunday 3 July 2011 at 3:24:15 PM, in
mid:fc521c32-4721-4721-930e-8536f83a2...@jabberwocky.com, David Shaw
wrote:
This will set your private key cipher to AES:
gpg --s2k-cipher-name aes --edit-key (thekey) passwd
save
Is there a
On Jul 3, 2011, at 12:15 PM, Chris Poole wrote:
On Sun, Jul 3, 2011 at 4:45 PM, David Shaw ds...@jabberwocky.com wrote:
There are some obscure edge cases where you must have a 3DES or AES encrypted
private key, but for the overwhelming majority of people, no, there is no
reason to do this.
Hi,
I changed the order of preferred ciphers and hash functions using setpref. My
public key has changed, but not the fingerprint.
Is the done thing now to ask anyone with the key to pull the latest version?
(I've already updated the keyserver version.)
Thanks
