<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tool on System Overlord</title><link>https://systemoverlord.com/tags/tool.html</link><description>Recent content in Tool on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Sat, 20 Jan 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/tool/index.xml" rel="self" type="application/rss+xml"/><item><title>socat as a handler for multiple reverse shells</title><link>https://systemoverlord.com/2018/01/20/socat-as-a-handler-for-multiple-reverse-shells.html</link><pubDate>Sat, 20 Jan 2018 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2018/01/20/socat-as-a-handler-for-multiple-reverse-shells.html</guid><description>&lt;p&gt;I was looking for a new way to handle multiple incoming reverse shells. My
shells needed to be encrypted and I preferred not to use Metasploit in this
case. Because of the way I was deploying my implants, I wasn&amp;rsquo;t able to use
separate incoming port numbers or other ways of directing the traffic to
multiple listeners.&lt;/p&gt;
&lt;p&gt;Obviously, it&amp;rsquo;s important to keep each reverse shell separated, so I couldn&amp;rsquo;t
just have a listener redirecting all the connections to STDIN/STDOUT. I also
didn&amp;rsquo;t want to wait for sessions serially &amp;ndash; obviously I wanted to be connected
to all of my implants simultaneously. (And allow them to disconnect/reconnect
as needed due to loss of network connectivity.)&lt;/p&gt;</description></item></channel></rss>