{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"Programming Tech Brief By HackerNoon","title":"Go's Cryptography Packages Were Audited: The Results ","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/7d27b8e0\"></iframe>","width":"100%","height":180,"duration":720,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/gos-cryptography-packages-were-audited-the-results.\n             The audit produced a single low-severity finding, in the legacy and unsupported Go+BoringCrypto integration, and a handful of informational findings. \n            Check more stories related to programming at: https://hackernoon.com/c/programming.\n            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.\n            \n            \n            This story was written by: @Go. Learn more about this writer by checking @Go's about page,\n            and for more stories, please visit hackernoon.com.\n            \n                \n                \n                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.\n        \n        ","thumbnail_url":"https://img.transistorcdn.com/KhCapPSRkLGL2Xw8888yuChkNRWthaKapLYTvNdu4W4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzQxMTY2LzE2ODM1/ODIzMzAtYXJ0d29y/ay5qcGc.webp","thumbnail_width":300,"thumbnail_height":300}