<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Projects on Shea Polansky</title><link>https://polansky.co/projects/</link><description>Recent content in Projects on Shea Polansky</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 29 Mar 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://polansky.co/projects/index.xml" rel="self" type="application/rss+xml"/><item><title>Burp HTTP Mock</title><link>https://polansky.co/projects/burphttpmock/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polansky.co/projects/burphttpmock/</guid><description>&lt;p&gt;While on an assessment for a client I needed a way to intercept certain HTTP API calls and dynamically generate a response while allowing other calls to go through to the real application&amp;rsquo;s servers. I came across an extension for &lt;a href="https://portswigger.net/burp"&gt;BurpSuite&lt;/a&gt; that allowed the user to select specific API calls to intercept and reply with &lt;em&gt;static&lt;/em&gt; content, but I needed the ability to &lt;em&gt;dynamically&lt;/em&gt; generate responses, so I added that functionality to the extension and published my changes. The extension now supports redirecting any HTTP request to any other URL, or replying to the call based on the contents of a file, or generating a response either by piping the content of the call to a program or by calling the program as a &lt;a href="https://en.wikipedia.org/wiki/Common_Gateway_Interface"&gt;CGI&lt;/a&gt; script.&lt;/p&gt;</description></item><item><title>IoT Village SAO</title><link>https://polansky.co/projects/iotvillagesao/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://polansky.co/projects/iotvillagesao/</guid><description>&lt;p&gt;As a fan of DEF CON&amp;rsquo;s &lt;a href="https://www.vice.com/en/article/vbne9a/a-history-of-badgelife-def-cons-unlikely-obsession-with-artistic-circuit-boards"&gt;#badgelife&lt;/a&gt;, I was ecstatic to have the opportunity to contribute as part of my employment at ISE. ISE runs the &lt;a href="https://iotvillage.org"&gt;IoT Village&lt;/a&gt; at DEF CON and at other conferences, and we wanted to have our own badge&amp;hellip; an effort which I unfortunately couldn&amp;rsquo;t see to completion while I was there.&lt;/p&gt;
&lt;p&gt;In the meantime, I worked with the marketing team at ISE to create this, the IoT Village official &lt;a href="https://hackaday.com/2019/03/20/introducing-the-shitty-add-on-v1-69bis-standard/"&gt;SAO&lt;/a&gt;. It features artwork by ISE&amp;rsquo;s talented &amp;lsquo;social media guy&amp;rsquo; cum salesman &lt;a href="https://www.linkedin.com/in/samuel-levin-16541294"&gt;Sam Levin&lt;/a&gt;. I worked with him to import the artwork into &lt;a href="https://kicad.org/"&gt;KiCAD&lt;/a&gt;, designed the rest of the PCB (it makes an LED glow, very complicated 😉), and oversaw the manufacturing process including cost optimizing the BOM and working with our PCB fabrication house to ensure the quality was up to spec.&lt;/p&gt;</description></item><item><title>Misc. Burp Tooling</title><link>https://polansky.co/projects/smallburptools/</link><pubDate>Sun, 29 Mar 2020 00:00:00 +0000</pubDate><guid>https://polansky.co/projects/smallburptools/</guid><description>&lt;p&gt;Much of my job consists of working with &lt;a href="https://portswigger.net/burp"&gt;BurpSuite&lt;/a&gt;, so I find myself regularly needing to write small custom tools for working with it. I publish the ones that I can in the hopes that someone else might find them useful. Here are the ones I&amp;rsquo;ve published so far:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/ise-spolansky/burp-extension-maven-archetype"&gt;Burp Extension Maven Archetype&lt;/a&gt; &amp;mdash; After writing a couple extensions I got tired of manually instantiating the project structure, so I wrote a &lt;a href="https://maven.apache.org/"&gt;Maven&lt;/a&gt; archetype that does it for me. One command gets you a project directory with the right imports and a copy of the PortSwigger &amp;ldquo;Hello World&amp;rdquo; demo extension&amp;rsquo;s code ready to modify into whatever you need.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ise-spolansky/burp-easy-request-saver"&gt;Burp Easy Request Saver&lt;/a&gt; &amp;mdash; Burp doesn&amp;rsquo;t have a fast way to export the binary contents of requests or responses, so I wrote one. It adds context menu entries to any request that lets you export the request or response headers or body to a file keeping all binary data intact. If you select multiple requests, each gets its own file.&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/ise-spolansky/Burp2Vegeta"&gt;Burp2Vegeta&lt;/a&gt; &amp;mdash; I was asked by a client to perform load testing on their service to simulate a Denial-of-Service attack. I decided to use &lt;a href="https://github.com/tsenart/vegeta"&gt;Vegeta&lt;/a&gt; to perform a classic request flooding attack, but I needed a way to quickly tell it how to send correctly-formatted API requests. As a result I wrote a small Burp extension that exports any request(s) as Vegeta JSON attack definitions to the system clipboard. You can then paste them into an attack definition file and fire away.&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>