<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Robert Tonic on The Trail of Bits Blog</title><link>https://miscreants.github.io/blog.trailofbits.com/authors/robert-tonic/</link><description>Recent content in Robert Tonic on The Trail of Bits Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 07 Nov 2019 07:00:06 -0500</lastBuildDate><atom:link href="https://miscreants.github.io/blog.trailofbits.com/authors/robert-tonic/index.xml" rel="self" type="application/rss+xml"/><item><title>Security assessment techniques for Go projects</title><link>https://miscreants.github.io/blog.trailofbits.com/2019/11/07/attacking-go-vr-ttps/</link><pubDate>Thu, 07 Nov 2019 07:00:06 -0500</pubDate><guid>https://miscreants.github.io/blog.trailofbits.com/2019/11/07/attacking-go-vr-ttps/</guid><description>The Trail of Bits Assurance practice has received an influx of Go projects, following the success of our Kubernetes assessment this summer. As a result, we’ve been adapting for Go projects some of the security assessment techniques and tactics we’ve used with other compiled languages. We started by understanding the design of the language, identifying […]</description></item></channel></rss>