Will this be implemented for RIPEMD-128 as well?
Regards,
Mattias
On Wednesday, April 24, 2002 5:51:18 PM UTC+2, Wei Dai wrote:
>
> You'll be able to use RIPEMD-160 with PKCS#1 after adding the
> following lines to pkcspad.cpp:
>
> template<> const byte PKCS_DigestDecoration<RIPEMD160>::decoration[] =
>
> {0x30,0x21,0x30,0x09,0x06,0x05,0x2b,0x24,0x03,0x02,0x01,0x05,0x00,0x04,0x14};
> template<> const unsigned int PKCS_DigestDecoration<RIPEMD160>::length =
> sizeof(PKCS_DigestDecoration<RIPEMD160>::decoration);
>
> This will be in the next release.
>
> On Wed, Apr 24, 2002 at 10:14:02AM +0200, Herr Nittel wrote:
> > At http://www.eskimo.com/~weidai/scan-mirror/sig.html#sem_PKCS1-1.5
> > RIPEMD-160 is listed as an allowed message digest.
> >
> > But crypto42, pkcspad.h, line 47 says:
> > // PKCS_DecoratedHashModule can be instantiated with the following three
> > // classes as specified in PKCS#1 v2.0.
> > class SHA;
> > class MD2;
> > class MD5;
> >
> > Is RIPEMD-160 in PKCS#1 v2.0 omitted?
> >
> >
> > --
> > Thomas Nittel
> >
> > mailto:[email protected] <javascript:>
> >
> >
> >
>
>
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
