On Thursday, January 24, 2019 at 12:08:05 AM UTC+2, Jeffrey Walton wrote:
>
>
>
> On Wednesday, January 23, 2019 at 11:09:49 AM UTC-5, Olli Savolainen wrote:
>>
>> Thank you Jeff. I appreciate it a lot.
>>
>> Basically I would like to convert the code in the first example (below)
>> to use anything safe to first sign the message with a private key and then
>> verify and extract with public key (the 'recovered' variable below).
>>
>
> I'm not really sure I understand your problem.
>
> Maybe you should use SHA256 instead of SHA1.
>
> Jeff
>
Thanks. The enums available seem to be SHA1 and SHA3.
Changing the enum value to SHA3 and the headers to match doesn't seem to
compile so apparently the example would need to be changed otherwise too.
How would you go about changing the SHA1 example code I posted? Sorry for
my simple questions, was just hoping for the exact same example code as you
have for SHA1 PSSR, but for a trusted algorithm. Thanks.
RSASS<PSSR, SHA1>::Signer signer(privateKey);
RSASS<PSSR, SHA1>::Verifier verifier(publicKey);
--
You received this message because you are subscribed to "Crypto++ Users". More
information about Crypto++ and this group is available at
http://www.cryptopp.com and
http://groups.google.com/forum/#!forum/cryptopp-users.
---
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/d/optout.
