> I think the mentioned "memory-hard KDF" is misleading. Scrypt is a PBKDF. >
I thought Percival described a class of problem and Scrypt was in the class (https://www.tarsnap.com/scrypt/scrypt.pdf). Is that no longer the case? Or did committees (like IETF and P1363) water it down so it no longer applied? (Committees do some unexpected things at times). Jeff -- -- 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.
