Subject: Ideas for graphics output - msg#00058

Previous Message by Date: click to view message preview

Re: Summer of Code

This would be awesome and I wish you luck. It would be hard for two reasons, though. 1. java is java, not C++. 2. Java MIDP is a POS^W^Wone of the worst-designed environments I've ever had the displeasure of using. Specifically in this case, what passes for sockets on MIDP are nearly unusable. Good luck! --Andy On 3/22/07, arun s <abelian77@xxxxxxxxx> wrote: > I am thinking of doing a college project of porting nmap to the java MIDP > environment so that it can be used on the mobile devices.I wanted to get > your feedback on this? > Can i doit through "summer of code"? > > _______________________________________________ > Sent through the nmap-dev mailing list > http://cgi.insecure.org/mailman/listinfo/nmap-dev > Archived at http://SecLists.Org > _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org

Next Message by Date: click to view message preview

Re: Ideas for graphics output

Personally I like to see the info about the OS, open ports etc for each host, but I'd also like to see the hosts interconected like cheops-ng does. The 3D representations are too messy to get any information quickly. By the way, I think it's important to use vector graphics so it doesn't look like crap when you resize the window, etc. Salud. Luis Martín. Francesco Pettene wrote: > Hello, > > i'd like to gather some opinions for my graphical Maps > application: any suggestion is appreciated. > > The are several paradigms around. > Starting from Adriano Monteiro's proposal: > > http://umit.sourceforge.net/umit_proposals_2007/umit_mapper1.png > > this is a very clear interface but lacks some important infos, > eg the links between routers and net-segments are not shown at > all, and this could be confusing comparing different networks. > This is solved in the Cheops-NG representation: > > http://cheops-ng.sourceforge.net/images/cheops.jpg > > UmitMapper describes graphically each host: > > http://umit.sourceforge.net/umit_proposals_2007/umit_mapper3.png > > according to me this information should pertain mostly to the > "regular" GUI (as in umit), but in the gfx output for each host > i could put in informations about the host vulnerability level > extrapolated from some db (eg CVE), latency, etc... > > My aim is to let the end user choose what informations to display > for the single hosts: this could be a sort of useful filter, since > the needed information pops out and you don't have to grep through > a long nmap output. > An example is this, where different ballons pop out: > > http://afterglow.sourceforge.net/screenshot3.jpg > > Last but not least, every gfx element should be as limited in size > as possible; beside, uninteresting hosts could be subjected to > culling... indeed the app needs to be scalable and render anything > from a small lan to *some* big networks. Representing all the hosts > in a class B would end up in gfx bloat, a graph explosion somewhat > like protein homology representation... d'oh! this scares me down! > > Two questions: > > - do you think 3d visualizations like these are confusing? > http://afterglow.sourceforge.net/screenshot1.jpg > http://projects.icapsid.net/fe3d/screens.html > > - what informations would you like to find for each host? > > Thanks. > > _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org

Previous Message by Thread: click to view message preview

a use pattern for nmap --- filtering for live hosts

Suppose you've got a source command that generates a list of hosts you should be interested in --- for some moderately expensive scan, and with some depressing percentage of dead hosts in the mix. Between the generator and the scanner, you can nmap -sP -iL - | awk '/appears to be up/{print $2}' for a fast filter to sort out the deadwood. -Bennett pgpByyYMAACu0.pgp Description: PGP signature _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org

Next Message by Thread: click to view message preview

Re: Ideas for graphics output

Personally I like to see the info about the OS, open ports etc for each host, but I'd also like to see the hosts interconected like cheops-ng does. The 3D representations are too messy to get any information quickly. By the way, I think it's important to use vector graphics so it doesn't look like crap when you resize the window, etc. Salud. Luis Martín. Francesco Pettene wrote: > Hello, > > i'd like to gather some opinions for my graphical Maps > application: any suggestion is appreciated. > > The are several paradigms around. > Starting from Adriano Monteiro's proposal: > > http://umit.sourceforge.net/umit_proposals_2007/umit_mapper1.png > > this is a very clear interface but lacks some important infos, > eg the links between routers and net-segments are not shown at > all, and this could be confusing comparing different networks. > This is solved in the Cheops-NG representation: > > http://cheops-ng.sourceforge.net/images/cheops.jpg > > UmitMapper describes graphically each host: > > http://umit.sourceforge.net/umit_proposals_2007/umit_mapper3.png > > according to me this information should pertain mostly to the > "regular" GUI (as in umit), but in the gfx output for each host > i could put in informations about the host vulnerability level > extrapolated from some db (eg CVE), latency, etc... > > My aim is to let the end user choose what informations to display > for the single hosts: this could be a sort of useful filter, since > the needed information pops out and you don't have to grep through > a long nmap output. > An example is this, where different ballons pop out: > > http://afterglow.sourceforge.net/screenshot3.jpg > > Last but not least, every gfx element should be as limited in size > as possible; beside, uninteresting hosts could be subjected to > culling... indeed the app needs to be scalable and render anything > from a small lan to *some* big networks. Representing all the hosts > in a class B would end up in gfx bloat, a graph explosion somewhat > like protein homology representation... d'oh! this scares me down! > > Two questions: > > - do you think 3d visualizations like these are confusing? > http://afterglow.sourceforge.net/screenshot1.jpg > http://projects.icapsid.net/fe3d/screens.html > > - what informations would you like to find for each host? > > Thanks. > > _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org