un-trusting MD5 in gpg

Werner Koch wk at gnupg.org
Thu May 7 19:36:58 CEST 2009

On Thu,  7 May 2009 19:14, dkg at fifthhorseman.net said:

> Can you explain what the problem is with having a more-specific error
> code?  We're talking about introducing new semantics in gpg already.
> Why not have an error code that specifically refers to those semantics?

There are already too many different error codes out of histroical
reasons.  Over the time I learned that many orf them are not very
usefule, whereas others are too broad.  These error codes are not only
for displaying someting to a user but mainly used as a small-bandwidth
notification system.  GnuPG acts on certain error codes and I can't see
how it should behave different on a disabled and a blacklisted also.  In
fact I am not sure whether we need them at all, we can display a custom
message to the user (or via --status-fd) and internally use the error
code for unknown algorithm.



Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.

More information about the Gnupg-devel mailing list