FYI... We experienced these failures on Master for a while. We had to switch to inline assembly to avoid the problem.
If your code was compiled with GCC, then you should ensure the self tests pass. The RDSEED tests will throw an Exception if the data is not compressible (its a poor man's entropy test). Jeff ---------- Forwarded message ---------- From: Florian Weimer <f...@deneb.enyo.de> Date: Thu, Jul 27, 2017 at 3:40 AM Subject: [oss-security] CVE-2017-11671: GCC generates incorrect code for RDRAND/RDSEED intrinsics To: oss-secur...@lists.openwall.com Earlier this year, a GCC bug was fixed which could lead to intrinsics for RDRAND and (more likely) RDSEED to produce non-random results. These instructions use the carry flag to report success or failure, and GCC used to generate instruction sequences which clobbered the flag before applications had a change to read it: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80180 https://gcc.gnu.org/ml/gcc-patches/2017-03/msg01349.html Practical impact is hopefully limited because the intrinsics are difficult to use due to an unrelated GCC usability issue, and inline assembly is not impacted by this issue. -- -- 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.
