I would like to add that we're not using RSA in this case. We instead use OAEP directly to randomize the input. Also, encryption (hiding the cleartext) is not a concern in this use case.
-sherman On Monday, March 24, 2014 10:59:38 PM UTC-5, Sherman Monroe wrote: > > Hi, > > I am working on a project that uses CryptoPP, and we wish to use the OAEP > class to provide protection against chosen cleartext attacks in our > protocol. I would greatly appreciate your insight on a detail of OAEP_Base. > > Question: The OAEP_Base method signatures do not appear as one would > expect for an OAEP padding scheme. These signatures suggest the encoding is > bytewise. But looking at the implementation, it appears the encoding is > bitwise. Can you please describe what the lengths passed into the message > are (are they bits, bytes, etc)? Also, can you provide two lines of code > which call these two functions? > > void Pad(RandomNumberGenerator &rng, const byte *raw, size_t > inputLength, byte *padded, size_t paddedLength, const NameValuePairs > ¶meters) const; > > DecodingResult Unpad(const byte *padded, size_t paddedLength, byte > *raw, const NameValuePairs ¶meters) const; > > Thank you in advance!! > > -sherman > -- -- 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/d/optout.
