Re: Some mod. info. references don't produce valid URLs

[Joshua TAYLOR <joshuaaaron () gmail com>]

On Wed, Aug 31, 2011 at 1:34 PM, HD Moore <hdm () metasploit com> wrote:
> On 8/31/2011 12:02 PM, Joshua TAYLOR wrote:
> > Hi all,
> >
> > I've been gathering some information programmatically from the
> > framework (loading the framework, iterating through modules, etc), and
> > have come across some reference info values that produce some invalid
> > URLs later (i.e., the SiteReference.site field of the reference isn't
> > a valid URL).
> >
> > I've observed this in two contexts.  The first is where a reference
> > should have a context id of 'URL' but has something else. E.g., the
> > auxiliary/scanner/dect/call_scanner module has
> <snip>
> > I don't know that the framework ever uses these values as URLs, so
> > it's not a bug in that sense, but the intent is that they should be
> > URLs (and that's what I'm looking for).  I've got a list of the
> > modules that contain these malformed entries;  what would be the
> > proper way to handle these?  A bug report?  Diffs on a developer list?
> >  Something else?
>
> Diffs would be great (msfdev () metasploit com or via Redmine), thanks for
> catching these!

OK, great.  It'll probably be a few days before I get around to this,
but they'll be on their way before too long.  I've actually got a few
other similar questions, too, (which will appear on the list shortly),
so there might be more to add anyhow.

-- 
Joshua Taylor, http://www.cs.rpi.edu/~tayloj/
_______________________________________________
https://mail.metasploit.com/mailman/listinfo/framework