Re: Zenmap Script UI

[Shinnok <admin () shinnok com>]

Hi Colin,

Adding some more tabs would only make Zenmap look bulkier.
Careful integration with the current tabs would make much more
usability sense, for eg. having the port scripts output expand under
each port when a link is pressed like David
suggested(http://seclists.org/nmap-dev/2011/q2/836) would be more
nicer but at the same tame imply a little bit more work and design.
Host scripts look pretty nice the way they're integrated as show in
your screenshot.

Additionally a *single* tab named scripts with all script results
available and properly categorized would be ok, however that's a
tricky one to design, since if it's going to look similar to the Nmap
output tab then probably it's not needed.

As for creating tabs for each and every type of scripts, It's a
definitely no-no for me. Is there some GUI designer for GTK/Python
that you currently use? If so then I would like to take a couple of
shots at the scripts tab.

Thanks,

On Tue, May 31, 2011 at 12:00 AM, Colin L. Rice <ricec2 () rpi edu> wrote:
> Hello,
>
> I've been working on adding script results to Zenmap. Parsing is done
> however we still have to design a UI. Attached is my proposed UI for the
> host scripts which is added to the host details panel.
>
> However there are three other script classes we have to deal with.
> Specifically Port Scripts, Prerule scripts and postrule script. Where
> would a logical place for this information be? How should it be
> presented?
>
> Obviously the port scripts should go in the port window somewhere.
>
> Ideas so far are:
> 1) having the port scripts be a additional hang off of the port window
> where you hit a button and the hosts go into the special mode where
> ports are hanging off of the hosts and when you click each port it shows
> the scrip details.
>
> 2)Add a column for script details which has an expansion button to let
> you see the scripts for that specific port.
>
> 3)Add a script tab and put recent pre and post scripts in there with a
> timestamp.
>
> 4)Add a script aggregation page somewhere under an existing tab
>
> 5)Have a popup for each pre and post script since they aren't that
> common and generally signal something important like duplicate ssh keys.
>
> If you have any comments or suggestions please respond.
>
> -Colin
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://seclists.org/nmap-dev/



-- 

Shinnok <http://shinnok.com>
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/