Re: A few UMIT problems/suggestions

[Kris Katterjohn <katterjohn () gmail com>]

Guilherme Polo wrote:
> > > > * I haven't done extensive testing yet, but at least on my Ubuntu box
> > > > when I try to Save the scan, I get a window pop up to choose where to
> > > > save the file and it just freaks out!  It's like there are two of them
> > > > sort of overlapping and it jumps between them or something.  It's hard
> > > > to explain and won't let me save the scan.  This is the only
> > > > window/option I've seen that this happens to, so I don't know how it
> > > > could be just me experiencing it because everything else seems to 
> > work fine.
> > > >
> > >
> > > It doesn't happen here (but that was using my branch).
> >
> > Hmm.. well, I don't know then :)
>
> I tested trunk and it didnt happen too ;/ is there something I can do
> to try to reproduce it ?

Sorry, nothing I can think of right now. I tried it and it just happened.

I'll let you know anything I figure out.  Maybe it's just some weird 
thing only happening to me :)

> > I have attached an XML file for a scan, and when opening in UMIT, I
> > still get 0 for filtered and closed when you can plainly see there are
> > plenty of each :)
> >
> > Does UMIT use the <extraports> XML directive (I think it's called)
> > correctly? That's where it is in this scan.
> >
> > This is a scan I did through Nmap and just opened through UMIT, so it
> > messes up both ways (through UMIT or just passed to it).
>
> First, thanks for the xml =) It helped me discover one bug in
> xmlstore, that stores the scans in Network Inventory. (xmlstore is
> part of new database schema that me and joao set up for umit). It also
> showed I was wrongly retrieving just first entry for extraports in
> database (new schema too).
>
> "standard UMIT" (trunk version) is using the same NmapParser I'm using
> in my branch, and it does shows correctly both extraports for filtered
> and closed state. But as it seems, the GUI is just showing ports
> closed when there is something like this: <port protocol="tcp"
> portid="22"><state state="closed" /><service name="ssh" method="table"
> conf="3" /></port>, and discarding extraport info for closed state.
> This is a bug to be reported too.

Glad I could help with that :)

I'll see about giving the SF bugtracker a try in just a little bit. 
Could I just use the umit-devel list for that instead? Are most of you 
guys subscribed?

In my experience, mailing lists usually seem to be better than bug 
tracking systems. But, maybe it's better now (or at least with you guys).


> Thanks again =)

Thanks,
Kris Katterjohn

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org