AMD Ryzen 3000 Post-Review BIOS Update Recap: Larger ST Gains, Some Gains/Losses

Re:AMD Ryzen 3000 Post-Review BIOS Update Recap: Larger ST G... by blattimwind on Sunday July 14, 2019 @11:31AM (#20433945)

People think that because it is correct. Any serious crypto library (libsodium, OpenSSL, crypto++, cryptlib, ...) that comes to mind uses this approach, codecs use it, your C standard library uses it etc.

[ Parent | on HN ]

Re:AMD Ryzen 3000 Post-Review BIOS Update Recap: Larger ST G... by Avamander on Sunday July 14, 2019 @11:32AM (#20433955)

But there's many other libraries out there than just those though?

[ Parent | on HN ]

Re:AMD Ryzen 3000 Post-Review BIOS Update Recap: Larger ST G... by blattimwind on Sunday July 14, 2019 @11:37AM (#20433970)

"One advantage of AMD over Intel is AMD included SHA hardware acceleration on every Ryzen processor."

What do you think is more common? People rolling their own SHA implementation or people calling <insert crypto library>'s SHA256()? The former will barely get any sort of optimization, regardless of compiler flags, the latter will automatically use the SHA extensions.

[ Parent | on HN ]

Re:AMD Ryzen 3000 Post-Review BIOS Update Recap: Larger ST G... by Avamander on Sunday July 14, 2019 @12:42PM (#20434362)

You indeed have a point about SHA extensions and people predominantly using a good crypto library, I guess I should've been more verbose that I meant new extensions in-general being a bit underutilized.

[ Parent | on HN ]