Sorry for the second mail, but I found two other points I wanted to make within this thread.
Am 17.10.2015 um 13:09 schrieb Jean-Pierre Münch: > > > Am 17.10.2015 um 02:39 schrieb Jeffrey Walton: >> Hi Everyone, >> >> There's a new wiki page on RDRAND at https://cryptopp.com/wiki/RDRAND. >> >> The generator was cut-in recently due to some off-list discussions, >> and it was approved by Wei. The download is not yet available, but it >> should be in the next couple of days. > Yippie, RDRAND support :) >> >> Open question: should the class file respond to DiscardBytes? I kinda >> feel like it should be a nop, but there could be folks who want to >> call it to increase their comfort level. > The promise of DiscardBytes() is, well, to discard bytes. If this > actually makes sense from a security standpoint or efficiency stand > point is not at us to judge, or we wouldn't have created this function > in the first place. If the user wants to discard 500 bytes, let him do > this via DiscardBytes() or he'll just write DiscardBytes() himself. >> >> Comments or suggestions are welcomed. > My suggestion is to also add RDSEED while we're working at it. > We'd then have to add a note that the user shouldn't call RDSEED for > large amounts of data but rather to seed PRNGs (along with > OSGenerateRandom() ). > > I'd volunteer to add RDSEED classes to this patch (and maybe rename it > to RDRNGs). > It was also confirmed [1] that AMD will also support RDSEED with the Zen architecture, this is the successor to the first AMD chip generation supporting RDRAND. Another point we may consider while we're at those hardware RNGs: TPMs. Windows 10 mandates a TPM 2.0 or a fTPM from launch for small devices and for larger devices beginning with 1 year post-release, this means that in the long run *every* Windows PC will have such a TPM (which is a good thing IMO). Now here comes the point: Those TPMs expose a RNG interface. Should we use it (via the OS)? As far as testing goes, I think I'll be able to perform those (Windows only) in 1-8 weeks. [1]: https://www.phoronix.com/scan.php?page=news_item&px=amd-zen-cpu-znver1 BR JPM >> >> 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] >> <mailto:[email protected]>. >> For more options, visit https://groups.google.com/d/optout. > > -- > -- > 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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- -- 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.
