Go's Cryptography Packages Were Audited: The Results
No se pudo agregar al carrito
Add to Cart failed.
Error al Agregar a Lista de Deseos.
Error al eliminar de la lista de deseos.
Error al añadir a tu biblioteca
Error al seguir el podcast
Error al dejar de seguir el podcast
-
Narrado por:
-
De:
This story was originally published on HackerNoon at: https://hackernoon.com/gos-cryptography-packages-were-audited-the-results.
The audit produced a single low-severity finding, in the legacy and unsupported Go+BoringCrypto integration, and a handful of informational findings.
Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #go, #golang, #go-cryptography-security, #go-security-audit, #go-cryptography-packages, #go-audit, #timing-side-channels, #hackernoon-top-story, and more.
This story was written by: @Go. Learn more about this writer by checking @Go's about page, and for more stories, please visit hackernoon.com.
Go ships with a full suite of cryptography packages in the standard library to help developers build secure applications. Google recently contracted the independent security firm [Trail of Bits] to complete an audit of the core set of packages. The audit produced a single low-severity finding, in the legacy and unsupported [Go+BoringCrypto integration], and a handful of informational findings.