Sorry, looks like you're right again. And sorry I'm coming up with just stupid ideas. Now I've actually done a test vs the CryptStringToBinary function and your base64decoding is working fine as far as I can see, on a small test data, plus the encryption parameters are coming out as the expected sizes, so likely it's something different...
Here's another random idea: could the Message XML have been incidentally transformed from the form it was originally in when hashed? I'm thinking namespaces... Have you successfully validated other data? Something I'm not clear on yet from looking through Crypto++ documentation is whether it is actually implementing only a preliminary version of PKCS #1 version 2.1 or the final version? On Aug 7, 5:55 pm, jztan <[EMAIL PROTECTED]> wrote: > but i'm using crypto++ for the RSASSA-PSS verification now. > as i now , crypto++ also process in Big-Endian too, isn't it ? --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
