[GSOC] ncat gui idea

[Shinnok <admin () shinnok com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I would like to probe my idea for this GSOC iteration
for nmap against the nmap-dev list. What I am thinking
about is a GUI for Ncat, written in native C++ code
and Qt. Full GUI customization using Qt Stylesheets
[http://doc.qt.nokia.com/latest/stylesheet.html], binary
cross platform compatibility and native looks for each
supported platform out of the box.
The native looks will be default, the stylesheets in
combination with QResource and Qt External Binary Resources
enable for a smart theme engine to be implemented.
I am also carefully considering about full flexibility
of the UI using QUiLoader.
These two combined will enable for interchangeable user interfaces
at runtime. This way one can achieve full ui customization.
I want users to be able to create or use ncat gui themes in the most
creative and unusual ways, from matrix console to bubbly
pink flower power to draconic dark sadistic themes/interfaces .

Cross platform native looks are taken care of by Qt(gtk lacks that). The
desktop platforms that Qt supports and provides native looks are
Linux(Gnome/KDE), Windows(by interogating uxtheme), Mac OS X. I already
have a sample interface that you guys can poke at:

http://shinnok.com/projects.php#ncgui

Take a look at the screenshots notice the native looks on KDE, GNOME
and Windows 7. Mac is out since I don't own one. :-)

It doesn't interface with ncat currently, though it's enough for
a gui idea poc. The interfacing with netcat i'm planning to do it via
UNIX pipes, either manually using dupes or libc popen() on *NIX,
and _popen() on Windows *.*. Another choice for interfacing agains
ncat would be to link against ncat's object files, though this effort
would be more valuable in the case of Nmap(see bellow).

Another reason that i am sending this e-mail is to probe the nmap's
team and community need for a new GUI for nmap. The ideas pointed
in this e-mail for Ncat were originally devised by me for a brand new
interface for Nmap that I would want and need. While I do realize
that Yet Another Gui(YAG) for Nmap would create fragmentation, it's the
kind of fragmentation that keeps open source *secure* and diverse.
Thus, what do you think about the same ideas written above, but applied
for Nmap(add the mobile and embedded advantages of Qt on top)?

Feel free to reply with ideas, corrections and improvements. I am
welcome to all kinds of constructive feedback on both the original
proposition Ncat and for the latter Nmap. Thanks!


Regards,

Shinnok

http://shinnok.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNjxVGAAoJEAzuYPBIYMpX53MH/RJ0uFP5zUHZuiCIimEn8Caw
BD59WLslmt7HMaAt8IreQBmmFgPOZdASylqsWmc+OWi5YmzCjaSelGRPhDTG+U0q
W6XuPkkVY3j7UQrxtpIIoBhGBygsyQFTIFxF7AXLMuqpGS1wg/LCkqDqInjDtb0p
SYQHlTsqUqWrrU02LHLKURrUpMnTuhH9Q4OtUh6YhvMdfh1x1vQ/ffUg53D7hxp4
hSQHaA5RYQnjFxVvR9uZWrVVKRPrUvEp1e7leErKyd+jK+Kz/TCJUXcVm61wBSPc
KlevznjGQl6IMVsM8C19pIh1OT6P2e6D58UkXhPBgkq00o0ntszAOowiE7cEStw=
=zT9M
-----END PGP SIGNATURE-----
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/