Re: Keygrip

2011-07-08 Thread Werner Koch
On Fri, 8 Jul 2011 00:06, li...@meumonus.com said: I'm trying to use the gpg-preset-passphrase command and it keeps failing. My thought is I'm not getting the keygrip correct. How do I discover the keygrip for a public certificate? With the stable 2.0 version of GnuPG the keygrip is only

Check that s2k-count has changed

2011-07-08 Thread Chris Poole
When changing my secret key's passphrase, I bumped up the s2k-count to 6553600 (I just added two zeros; I don't notice any slow down when decrypting on a Core2Duo). How can I confirm that this count is being used? I ran gpg --list-packets ~/.gnupg/secring.gpg, which told me a number for protect

Re: Check that s2k-count has changed

2011-07-08 Thread David Shaw
On Jul 8, 2011, at 10:10 AM, Chris Poole wrote: When changing my secret key's passphrase, I bumped up the s2k-count to 6553600 (I just added two zeros; I don't notice any slow down when decrypting on a Core2Duo). How can I confirm that this count is being used? I ran gpg --list-packets

Re: Check that s2k-count has changed

2011-07-08 Thread Daniel Kahn Gillmor
On 07/08/2011 12:31 PM, David Shaw wrote: Yes. Note that the list-packets output shows the internal packed value: 6553600 should come out to 201. The default of 65536 would encode to 96. You might file an enhancement bug to print the decoded value in --list-packets. We already print it

Re: Check that s2k-count has changed

2011-07-08 Thread Chris Poole
On 8 Jul 2011, at 17:31, David Shaw ds...@jabberwocky.com wrote: Yes. Note that the list-packets output shows the internal packed value: 6553600 should come out to 201. The default of 65536 would encode to 96. I do indeed get 201. Out of interest, how is that calculated? I also changed the

Re: Check that s2k-count has changed

2011-07-08 Thread Hauke Laging
Am Freitag, 8. Juli 2011, 20:35:57 schrieb Chris Poole: On 8 Jul 2011, at 17:31, David Shaw ds...@jabberwocky.com wrote: Yes. Note that the list-packets output shows the internal packed value: 6553600 should come out to 201. The default of 65536 would encode to 96. I do indeed get 201.

Re: Check that s2k-count has changed

2011-07-08 Thread David Shaw
On Jul 8, 2011, at 2:35 PM, Chris Poole wrote: On 8 Jul 2011, at 17:31, David Shaw ds...@jabberwocky.com wrote: Yes. Note that the list-packets output shows the internal packed value: 6553600 should come out to 201. The default of 65536 would encode to 96. I do indeed get 201. Out of

Re: Check that s2k-count has changed

2011-07-08 Thread Chris Poole
Thank you. On 8 Jul 2011, at 20:06, Hauke Laging mailinglis...@hauke-laging.de wrote: Am Freitag, 8. Juli 2011, 20:35:57 schrieb Chris Poole: On 8 Jul 2011, at 17:31, David Shaw ds...@jabberwocky.com wrote: Yes. Note that the list-packets output shows the internal packed value: 6553600

Re: Check that s2k-count has changed

2011-07-08 Thread Chris Poole
Thanks for the detailed response. I've done some C programming so it's not too alien to me. I don't know if this would be of any real use (perhaps just for those that are pretty sure of the slowest machine they'll be decrypting their private key on), but a function to calculate how many rounds