Slashdot Mirror
Wireshark Switches To Qt
An anonymous reader writes "Beginning with version 1.11.0, open source packet analyzer Wireshark is switching its user interface library from GTK+ to Qt. 'Both libraries make it easy for developers [to] write applications that will run on different platforms without having to rewrite a lot of code. GTK+ has had a huge impact on the way Wireshark looks and feels and on its popularity but it doesn't cover our supported platforms as effectively as it should and the situation is getting worse as time goes on.'"
I can't say that I really mind. I like to try to use mostly GTK based apps but it still falls down to the quality of the app. I use qBittorrent as my Torrent client because it works better than Deluge or any other GTK client I've found. Particularly when set to the same theme QT is just fine.
"People who think they know everything are very annoying to those of us who do."-Mark Twain
VLC, Maemo, TwimGo, LXDE; I for one would like to see a future where GIMP is the only major application left using GTK. Poetic justice.
What exactly are you concerned about them loosing? Maybe some horrible monster they've been keeping in their basement? Or a bio-genetic plague?
loosing? really?
This is a big win for the Qt ecosystem. Between KDE libraries reworked into portable Qt modules and official iOS and Android support even with support from Digia-- Qt is gaining momentum. They even managed to survive being gobbled by Nokia, then being sold to Digia-- it has been a bumpy ride.
I recently tried out the latest Kubuntu and have been loving it installed on an old Dell D410 (12inch, 1.8Ghz SC Pentium, 1.5G RAM) laptop and it runs well and does everything I need (which in this case is Qt related application development :-)
That's not what I meant.
There you go, "Gnome" with all your bullshit misunderstanding of how a GUI is intended to look like. Go Qt!
What exactly are you concerned about them loosing? Maybe some horrible monster they've been keeping in their basement? Or a bio-genetic plague?
Why can't you just tow the line and give him free reign? It passed the spell checker, isn't that all that counts?
Gtk used to stand for the gimp toolkit, but more and more it's the gnome toolkit. I wouldn't be surprised to see it merged into the gnome framework entirely at and future date. Even the mailing list is now renamed to gnome-list.
It's still a great toolkit, and still somewhat cross-platform. It's still being actively worked on on Windows and Mac osx. But with the focus mainly on gnome and Linux (gnome 3 has little support for other platforms now) they are not as advanced or stable ports.
I think wireshark's move to qt is a good one. Will definitely lead to better apps on Windows and Mac.
Loose, v.: pass. and intr. To finish working; (of a school, factory, etc.) to close, disperse, ‘break up’.
If you like historicisms, there's also: intr. To crumble away; to dissolve, melt. Or even transf. To relax or loosen (the bowels). Yeah, the last one could be accurate. I hope they have their brown pants at the ready. :-)
Ezekiel 23:20
Not... a... typographical error!!!
W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
Worse. Much worse.
More code.
I'd like to see it ported to WINGs. It's simple, fast, pretty and not married to C++.
Stick Men
When last I heard, a few years ago, QT had been acquired by Nokia. More recently, it seems that Nokia is being acquired by the borg(Microsoft).
It would seem that QT is to be owned by Microsoft. Is this correct? If so, what does that hold for QT? I realize that QT is LGPL or some such, but that doesn't mean that Microsoft won't ruin it or snuff it out. See Oracle and MySQL for a road map. Hopefully I am wrong.
It should have read: "Why can't ewe just tow the line and give him free rain?
The "reign" was already wrong - the correct word would have been "rein". Not quite as much fail as at first sight?
Need to type accents and special characters in Windows? Use FrKeys
A Beowulf cluster of grammar Nazis!
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
GTK+ was outrageously superior to anything out there about 5 years ago and today it's a declining community without clear goals and without strong support from developers that need this kind of library. I don't fully understand all the details that make this happened, but I clearly remember that about 2 or 3 years ago, something changed radically when Nokia changed the Qt license and when the Gnome leaders started to act against there own community with the suicidal Gnome 3 project.
There nothing to hope when a few peoples take the power to deny the criticisms from a large part of there community. The community simple change to get away from the toxic. That's the strong power of the open source, and it's a shame that leaders from leading open source project don't understand that simple rule.
In a ideal world GTK+ and QT should have merged there most valuable features in a new neutral project as soon as QT was fully open source. Real developers don't car about the name of the project as long as the quality and the community are driving the project up to the edge of there expectations.
I don't use software that chmods or chown mydirectories. Wireshark has done so. Citation? Look it up. Wireshark sucks.
Well, I looked it up, and there are no chmod or chown calls in the Wireshark source (trunk, 1.10, or 1.8), and there are no obvious pages found by Teh Google about this.
Citation (and, no, "look it up" isn't a citation, it's a trick used by people who don't actually have citations) or it didn't happen.
I fired up wireshark and did a data capture just to test the software. But what I was looking for was the way you could watch a interface pre 2000 like with blackice. Anyone know what software you could do that with today?
I don't use software that chmods or chown mydirectories. Wireshark has done so. Citation? Look it up. Wireshark sucks.
To fully access the data stack from eth0 or wlan0 you need to run wireshark as root otherwise your trace will not be complete. The result is that the files created by wireshark then are owned by # not $
All packet sniffers technically need to have root to be effective on any Unix like system. All you have to do is chown the output files and you can edit and delete them to your hearts content. Technically wireshark does not change the ownership of any directories but only inherits root because it is run as root so any directories or files that it creates are the property of root.
Wireshark is a great tool but it requires higher privilege to do the job it does. For a core logging piece of software it is very good and does not eat up resources like other ones that I have run over the years. One thing though if you turn down the verbosity level of the output so that it does less prefixing it sure helps to keep the output file size down, the default output is a little too verbose and includes too much unneeded spacing and device descriptions at all the start and stop requests. Sometimes if you are tracking a malicious web site bounce pattern it is nice to not have to wade through 30-40 meg of text data just to see a few dozen server hops!
A few weeks back tracking down a simple vbulletin hacked to do linkbucks scam site bounces created over 60 meg of data that I had to search through for the offending server sites, thank heavens for the line numbering capabilities and search features in Kate!
The use of Wireshark without a doubt helps keep servers clear of these assholes if it wasn't for a crowd of people tracking the linkbucks malware slinging assholes down and getting them kicked off servers using MS Windows on the net would be down right impossible.
This message was not sent from an iPhone because Peter Sellers really was a deviated prevert without a dime for the call
To fully access the data stack from eth0 or wlan0 you need to run wireshark as root otherwise your trace will not be complete.
Nope.
For one thing, Wireshark shouldn't be accessing the network interfaces, it should be asking the dumpcap program, which is one of the components of Wireshark, to do so. To quote Wireshark's README.packaging file:
For another thing, the README.packaging document (in the "Privileges" section, which contains that rather emphatic quote), and the CaptureSetup/CapturePrivileges page in the Wireshark Wiki, discuss ways in which you can avoid even running dumpcap as root - it may need additional privileges, but not full root privileges.
All packet sniffers technically need to have root to be effective on any Unix like system.
Nope. See the above documents and the main libpcap man page (following "Reading packets from a network interface may require that you have special privileges:"). That's what the ChmodBPF script installed by Wireshark on OS X does; see the "Under BSD (this includes Mac OS X)" section - it does the "some other way to make that happen at boot time".
This message was not sent from an iPhone because Peter Sellers really was a deviated prevert without a dime for the call
Presumably he had to answer to the Coca-Cola company for that?
To fully access the data stack from eth0 or wlan0 you need to run wireshark as root otherwise your trace will not be complete.
Nope.
For one thing, Wireshark shouldn't be accessing the network interfaces, it should be asking the dumpcap program, which is one of the components of Wireshark, to do so. To quote Wireshark's README.packaging file:
For another thing, the README.packaging document (in the "Privileges" section, which contains that rather emphatic quote), and the CaptureSetup/CapturePrivileges page in the Wireshark Wiki, discuss ways in which you can avoid even running dumpcap as root - it may need additional privileges, but not full root privileges.
All packet sniffers technically need to have root to be effective on any Unix like system.
Nope. See the above documents and the main libpcap man page (following "Reading packets from a network interface may require that you have special privileges:"). That's what the ChmodBPF script installed by Wireshark on OS X does; see the "Under BSD (this includes Mac OS X)" section - it does the "some other way to make that happen at boot time".
This message was not sent from an iPhone because Peter Sellers really was a deviated prevert without a dime for the call
Presumably he had to answer to the Coca-Cola company for that?
Ok Thanks I am running the older version LOL
$ wireshark --version wireshark 1.4.6 Copyright 1998-2011 Gerald Combs and contributors. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled (32-bit) with GTK+ 2.24.4, with GLib 2.28.6, with libpcap 1.1.1, with libz 1.2.3.4, with POSIX capabilities (Linux), without libpcre, with SMI 0.4.8, with c-ares 1.7.3, with Lua 5.1, without Python, with GnuTLS 2.8.6, with Gcrypt 1.4.6, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built Mar 18 2011 15:44:36), without AirPcap. Running on Linux 2.6.38-8-generic, with libpcap version 1.1.1, with libz 1.2.3.4, GnuTLS 2.8.6, Gcrypt 1.4.6. Built using gcc 4.5.2. ~ $
Guess I should upgrade and RTFM. I only use it when doing single traces though so the chances of leaving something open and being hacked while using it are almost zero, I do not run it as a process on the server only as a tracking mechanism if something gets hacked and then only on a the old laptop that I use for diagnostics. I should set it up as a service though if I can figure out an effective way to keep the log sizes down to specific info instead of a verbose as hell text file! Would be great if the files it created could be time stamped and compressed by wireshark itself on the fly as it logs. I tried setting up a cron with a shell script to do that but could not get it to spawn an output text log. Guess I should hone up my bash skills and do some more RTFM. Hopefully wireshark can use automated scripts to setup logging with a cron job without running a the gui something like the way I run vlc nox.
This message was not sent from an iPhone because Peter Sellers really was a deviated prevert without a dime for the call
Well with GTK+ being cross platform, Wireshark on MacOS still required using the X Windows interface. So will the move to Qt finally make it a native app?
Wireshark doesn't require X11, GTK2 does.
So when you've installed GTK2 via Macports like this
gtk2 @2.24.21_0+no_x11+quartz+universal
then wireshark isn't using X11 and feels like a native MacOS-Application:
- Wireshark-Dockicon
- No X11 is started
- The menubar is on top, like in any other mac-applcation
regards
There are only 10 types of people in the world: Those who understand binary and those who don't.
Wireshark isn't for crybabies anyway.
I want this account deleted.