<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>ClearNet Security: Tag ror</title>
    <link>http://blog.clearnetsec.com/articles/tag/ror</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>nmap junkie?  </title>
      <description>&lt;p&gt;We&#8217;re playing w/RoR and building a few web apps.  I wrote a quick and easy one that helps you build a command line for nmap, nothing particularly special.
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://nmapTweaker.clearnetsec.com/"&gt;http://nmaptweaker.clearnetsec.com/&lt;/a&gt; 
&lt;/p&gt;
&lt;p&gt;
I did add some extra content:  tuning tips, examples, and a time estimator.  Basically you can use it to build a command line, then copy and paste it to wherever you want to run it.
&lt;/p&gt;
&lt;p&gt;
It does not do syntax checking for nmap options which require input yet (e.g. targets, output file name, etc.), but the app does do some error checking for conflicting options.    
&lt;/p&gt;
&lt;p&gt;
It&#8217;s a little rough, but hey, it &lt;i&gt;might&lt;/i&gt; save you a few minutes of time if you&#8217;re not an nmap option sage.  
&lt;/p&gt;

</description>
      <pubDate>Thu, 23 Nov 2006 23:02:00 -0700</pubDate>
      <guid isPermaLink="false">urn:uuid:27227f77-be7e-4ac3-8b13-5d2069acc935</guid>
      <author>tate@ClearNetSec.com (Tate Hansen)</author>
      <link>http://blog.clearnetsec.com/articles/2006/11/23/nmap-junkie</link>
      <category>nmap</category>
      <category>port  scanning</category>
      <category>ClearNet Security</category>
      <category>Tate Hansen</category>
      <category>ror</category>
    </item>
  </channel>
</rss>
