Go Security
summary
Go security panel describes concrete work: a fuzzing in standard library rollout that becomes beta imminently to run fuzz targets like tests; a centralized vulnerability database plus tooling that uses call-graph analysis to warn only when vulnerable code is reachable; recommendations and fixes for common bugs (missing HTTP timeouts, forgetting to close response bodies) and long-running tradeoffs such as whether to address known html/template problems like issue 9200.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:02Katie Hochman
- 8:40What Is What Are the Main Responsibilities of the Go Security Team
- 15:57The Vulnerability Database
- 16:52Tracking Vulnerabilities
- 20:43Your View on Providing a Secure by Default and Hard To Misuse Client Server Implementation for Common Protocols Such as Http
- 29:02Closing a Response Body
- 34:43How Do People Report Vulnerabilities
- 49:01What's the Most Common Security Issue You Find with Open Source Projects
related talks
45mEssential security checks for your Go project
31mGo Security – Past, Present, and Future
25mExploring Some Essential Security Checks for Any Open Source Go Project
27mSecurity: The Thing That Everyone...
32mSecure and reliable development with Go
05mLightning Talk: Improving The Security Of Your Go Applications
01h 01mSoftware Security
51mSecurity & Privacy in Digital First Businesses (Panel)