Bug#570651: ssh-vulnkey: uncommon behaviour in return values

[redshift <redshift@gmx.com>]

Package: openssh-client
Version: 1:5.1p1-5
Severity: wishlist

In the man page it can be read:

"EXIT STATUS
 ssh-vulnkey will exit zero if any of the given keys were in the
compromised list, otherwise non-zero."

 While this describes correctly the behaviour of the utility, I don't
agree it is a useful solution. While scripting (and checking for return
values) I would expect a non-zero exit status when there is some action
to be taken (in this case, a corrupted key), or a clean (zero) exit
status when there's nothing to worry about.

 Is there any particular reason why ssh-vulnkey should be one of the few
software (if not the only one) allowed to do right the opposite?

Best regards