gnupg 1.4.2 import time errors

David Shaw dshaw at jabberwocky.com
Tue Aug 23 05:30:31 CEST 2005


On Mon, Aug 22, 2005 at 07:20:50PM -0700, Parag Mehta wrote:
> can some one help me understand this. why do i get this on every new
> release of gnupg that i start using when a new release is available. is
> there way to fix this permanently ?
> 
> gpg: algorithms on these user IDs:
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 1
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 0
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 0
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 0
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 0
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 0
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 0
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 0
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 0
> gpg:          "Parag Mehta <pmehta at pmehta.com>": preference for cipher
> algorithm 0
> gpg: it is strongly suggested that you update your preferences and
> gpg: re-distribute this key to avoid potential algorithm mismatch problems

Do:

  gpg --edit pmehta at pmehta.com
  setpref
  save

Then send the key to the keyservers again.

However, it is interesting to note that your key is slightly corrupt
(there is no cipher algorithm 0, though your key has it set as a
preference).  Did you edit your preferences at one point?  And if so,
what program did you use?

David



More information about the Gnupg-users mailing list