<?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>Offensive Security on heapspray.io - a plethora of infosec garbage</title>
    <link>https://heapspray.io/categories/offensive-security/</link>
    <description>Recent content in Offensive Security on heapspray.io - a plethora of infosec garbage</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 22 Apr 2015 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://heapspray.io/categories/offensive-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Metasploit soul-searching: scanning with metasploit</title>
      <link>https://heapspray.io/posts/metasploit-soul-searching-part-i-scanning-with-metasploit/</link>
      <pubDate>Wed, 22 Apr 2015 00:00:00 +0000</pubDate>
      <guid>https://heapspray.io/posts/metasploit-soul-searching-part-i-scanning-with-metasploit/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been trying to expand my knowledge of Metasploit recently. I&amp;rsquo;ve
gotten training which included quite extensive coverage of the
framework, for which I&amp;rsquo;m grateful; but to really get how extensive the
tool&amp;rsquo;s functionality is, there&amp;rsquo;s nothing quite like practice.&lt;/p&gt;
&lt;p&gt;With this in mind, I downloaded the metasploitable VM over at
sourceforge
(&lt;a href=&#34;http://sourceforge.net/projects/metasploitable/files/Metasploitable2/&#34;&gt;http://sourceforge.net/projects/metasploitable/files/Metasploitable2/&lt;/a&gt;)
and began hacking away at it.&lt;/p&gt;
&lt;p&gt;When you start working on these things, it&amp;rsquo;s awful tempting to fall back
into &amp;lsquo;CTF mode&amp;rsquo;, where your only objective is to get in. It&amp;rsquo;s not super
effective in testing the tool, though. So I tried to limit myself to
metasploit only, and see how far I could go. I also took a breadth-first
approach rather than a depth-first approach - in other words, exploring
as many of the scanning functionality as possible before moving on to
exploitation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>WebSockets</title>
      <link>https://heapspray.io/posts/websockets/</link>
      <pubDate>Fri, 14 Mar 2014 00:00:00 +0000</pubDate>
      <guid>https://heapspray.io/posts/websockets/</guid>
      <description>&lt;p&gt;WebSockets are a mechanism that allow a client (typically a web page) to
talk to a server without the overhead and complications that web
services may pose. The client first establishes a connection using http
and then makes a request to switch over to websockets; the process is
described in &lt;code&gt;RFC 6455 &amp;lt;https://tools.ietf.org/html/rfc6455&amp;gt;&lt;/code&gt;__. Using
this technology simplifies development of elaborate web based clients
and reduces web traffic, which is pretty sweet for developed and admins
alike&lt;/p&gt;</description>
    </item>
    <item>
      <title>VNC passwords</title>
      <link>https://heapspray.io/posts/vnc-passwords/</link>
      <pubDate>Wed, 12 Mar 2014 00:00:00 +0000</pubDate>
      <guid>https://heapspray.io/posts/vnc-passwords/</guid>
      <description>&lt;p&gt;We like to think of VNC passwords as encrypted; but when you consider
that they&amp;rsquo;re encrypted using DES (a weak encryption algorithm) with a
key that is hardcoded&amp;hellip; Well&amp;hellip; That pretty much makes VNC
passwords \ &lt;em&gt;encoded&lt;/em&gt; and not \ &lt;em&gt;encrypted&lt;/em&gt;. There are a few VNC
password revealers out there, such
as \ &lt;code&gt;vncpwd &amp;lt;https://github.com/jeroennijhof/vncpwd&amp;gt;&lt;/code&gt;__ or &lt;code&gt;VNCPassView &amp;lt;http://www.nirsoft.net/utils/vnc_password.html&amp;gt;&lt;/code&gt;__,
the former can be used in Linux and the latter in Windows. A
prerequisite to using these is that you have access to the VNC passwd
file and/or registry. Other tools exist to snarf the VNC password out of
network captures.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
