On Thursday, January 24, 2019 at 2:58:54 PM UTC+2, Jeffrey Walton wrote: > > > > On Thursday, January 24, 2019 at 6:49:22 AM UTC-5, Olli Savolainen wrote: > >> >> 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); >> >> > Please change the hash to SHA256 and then show the exact error you are > receiving. Copy and paste it from the terminal. >
Oh thanks, that actually seems to work. I had just forgotten the using directive so it seemed like SHA256 enum value didn't seem to work. Just curious, why is SHA3 different, or have I just messed up somehow? Anyway, can I help with updating the example so newcomers can immediately find an example that is for a trusted example? -- 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
