I should add a couple points here: > The OMP gear is guarded by an OMP if clause dependent upon CRYPTOPP_RW_USE_OMP. We were not able to improve performance for the class by utilizing OMP.
The OMP if clause is available from the first standard, which was 1.0. So the if clause will not break compiles on older gear. Assuming we use a similar patter in the future, the expedient way to enabling en-masse will be with sed. Something like `sed -i s/USE_OMP = false/USE_OMP = true/g`. That will capture CRYPTOPP_RW_USE_OMP (and others *if* implemented, like CRYPTOPP_RSA_USE_OMP). Jeff On Monday, June 29, 2015 at 11:33:46 AM UTC-4, Jeffrey Walton wrote: > > Below is the next patch planned for Rabin-Williams. It improves efficiency > of the signature scheme while maintaining compatibility with P1363 and > preserving existing behavior. > > The class members used in precomputation are mutable so Precompute can be > called from const member functions. The precomputation does not modify the > RW proper parameters, like n, p, q and u. > > The OMP gear is guarded by an OMP if clause dependent upon > CRYPTOPP_RW_USE_OMP. We were not able to improve performance for the class > by utilizing OMP. > > Optional blinding was removed in favor of a "better" planned cut-in. > Blinding applies to many (all?) integer factorization based problems, so it > should be more than a one-off cut-in. > > The fix for CVE-2015-2141 was already committed. > > Comments are welcomed. > -- -- 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.
