How to Catch Malware Errors Using Go

Ivan Kwiatkowski joins Natalie once again for a follow-up episode to Hacking with Go: Part 2. This time we’ll get Ivan’s perspective on the way Go’s security features are designed and used, from the user/hacker perspective. And of course we will also talk about how AI fits into all this…

Join the discussion

Changelog++ members save 4 minutes on this episode because they made the ads disappear. Join today!

Sponsors:

• Sourcegraph – Transform your code into a queryable database to create customizable visual dashboards in seconds. Sourcegraph recently launched Code Insights — now you can track what really matters to you and your team in your codebase. See how other teams are using this awesome feature at about.sourcegraph.com/code-insights
• FireHydrant – The reliability platform for every developer. Incidents impact everyone, not just SREs. FireHydrant gives teams the tools to maintain service catalogs, respond to incidents, communicate through status pages, and learn with retrospectives. Small teams up to 10 people can get started for free with all FireHydrant features included. No credit card required to sign up. Learn more at firehydrant.com/

Featuring:

• Ivan Kwiatkowski – GitHub, Mastodon, X
• Natalie Pistunovich – GitHub, X

Show Notes:

• Hacking with Go: Part 1
• Hacking with Go: Part 2
• Pascal (programming language)
• Hacking tool: IDA Pro
• Hacking tool: Ghidra
• Stowaway – Multi-hop Proxy Tool for pentesters
• Ivan’s video on reversing a Go malware
• “Stylometry” - recognizing author by code style, talk from the CCC 2014

Something missing or broken? PRs welcome!