What I *could* imagine what *may* be useful in the future (no concrete requests and if I had some I'd just add them straight away when preparing my code):
> - Tree hashing (setup) related parameters, i.e. TreeLeafSize, TreeFanOut, > TreeMaxHeight > - for KDFs: KeyIdentifier (separate from personalization) > - for KDFs: PublicKey(+ -Size) (for digital signature hashing) > - on-the-fly: PHC parameters (i.e. MCost, TCost, Scrypt's p,r,n, ...) > > Those are only ideas, as I said, any new names I need, I will add them > while I'm implementing (just like I did with the OIDs ;) . > I don't believe OIDs should be added to Argnames. I think there's a registry of curve names to OIDs in eccrypto. But we can look over your use of them if you present something. > I don't think we need them now, but maybe in the future (I got the first > three points from the Skein spec). > OK, so I'm clear... Is it NO, you don't need anything added? Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com. 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 cryptopp-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
