I have just built version 5.5.2 of crypto++ and it worked fine! This
was a good excuse for moving forward...
Thanks for the hints...


By the way, will 5.5.2 be FIPS certified at some point?

Christian

On Sep 29, 9:09 pm, greatx <[EMAIL PROTECTED]> wrote:
> Hi Wei,
>
> I am using:
> -Crypto++ Version 5.2.1   7/21/2004
> -MSVC++ 6 with SP5 and the processor pack
> -WindowsXP professional SP2
>
> The error compiling:
> error C2065: 'SHA224' : undeclared identifier - for the line that
> says:
> ECDSA<ECP, SHA224>::PrivateKey kpriv;
>
> Am I using a version that is too old? Maybe I should more to 5.5.2? (I
> need to keep using MSVC++ 6 SP2 for other projects)
>
> Thank  you.
>
> Christian
>
> On Sep 29, 6:25 pm, "Wei Dai" <[EMAIL PROTECTED]> wrote:
>
>
>
> > It works fine for me with MSVC 2005 and Crypto++ 5.5.2. Please post the
> > following information if you want further help:
>
> >     *  exact error message
> >     * version of Crypto++, operating system (output of "uname -a" command if
> > using Unix), and compiler (output of "gcc -v" if using GCC)
>
> > --------------------------------------------------
> > From: "greatx" <[EMAIL PROTECTED]>
> > Sent: Saturday, September 29, 2007 1:34 PM
> > To: "Crypto++ Users" <[EMAIL PROTECTED]>
> > Subject: Is SHA224 supported for ECDSA<ECP, SHA224>? - urgent
>
> > > I need to use the folowing:
>
> > > ECDSA<ECP, SHA>::Signer sig1;
> > > ECDSA<ECP, SHA224>::Signer sig224;
> > > ECDSA<ECP, SHA256>::Signer sig256;
>
> > > but I see that SHA224 does not build. Is this not supported in crypto+
> > > +?
> > > If not, then how can I make it work somehow?
>
> > > Thank you.
> > > Christian- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -


--~--~---------~--~----~------------~-------~--~----~
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.
-~----------~----~----~----~------~----~------~--~---

Reply via email to