> Can I ask you to take a look at the attached patch?  It is not yet
> satisfactory (at least, it needs to be forwardported to the CVS
> version, as I worked against 5.2.1 because I wanted to install this
> ASAP on my Debian boxen), but maybe we can start from this to discuss
> what needs to be done.  It implements sha224, sha256, sha384 and
> sha512.

Would it make more sense to have a single sha utility that takes
an argument of which algorithm to use, defaulting to the most
secure, then the user can define wrappers to invoke a non-default
algorithm?  For example, 'sha --algorithm=sha224' or 'sha --224'?

--
Eric Blake




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to