Beta

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Wireshark Switches To Qt

Soulskill posted about 9 months ago | from the changing-horses dept.

GUI 79

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.'"

cancel ×

79 comments

Sorry! There are no comments related to the filter you selected.

Meh (2)

MBGMorden (803437) | about 9 months ago | (#45167509)

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.

Re:Meh (-1)

Anonymous Coward | about 9 months ago | (#45167823)

Qt is a real man's application programming library. GTK is for designers who shove their FagPhones up their's and their boyfriend's asses.

Re:Meh (1, Funny)

Anonymous Coward | about 9 months ago | (#45168587)

GTK is not called the Gay ToolKit for nothing!

Re:Meh (1)

larry bagina (561269) | about 9 months ago | (#45171919)

ahem, that's GIMP ToolKit. Not all gimps are gay.

Re:Meh (2)

intermodal (534361) | about 9 months ago | (#45167895)

The quality of applications is all I've come to care about. I used to be the same about trying to use GTK, but I just can't bring myself to ditch a superior program for an inferior one just because of which toolkit they use. License for their code? Sure. GTK vs QT? Meh.

Dropping like flies. (-1)

Anonymous Coward | about 9 months ago | (#45167519)

When major applications like Wireshark start switching interface libraries, you know that the Gnome team can't stick around too much longer as the market leader in the Linux interface world.

There goes another one (4, Interesting)

krkhan (1071096) | about 9 months ago | (#45167547)

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.

Re:There goes another one (1)

Anonymous Coward | about 9 months ago | (#45167923)

I really want to see gimp ported to Qt. That would be hilarious. We could call it qtImp, pronounced "cute imp."

Re:There goes another one (1)

K. S. Kyosuke (729550) | about 9 months ago | (#45167999)

Replace the interface, and then replace the imaging kernel. What remains?

Re:There goes another one (0)

Anonymous Coward | about 9 months ago | (#45168435)

The dumb name.

Re:There goes another one (1)

X0563511 (793323) | about 9 months ago | (#45168045)

GIMP isn't named GIMP because it used GTK.

Re:There goes another one (5, Informative)

doti (966971) | about 9 months ago | (#45168137)

It's just the opposite. GTK is named after GIMP.

GIMP is GNU Image Manipulation Program

GTK is GIMP ToolKit

Re:There goes another one (1)

K. S. Kyosuke (729550) | about 9 months ago | (#45168297)

They'd have to rename it to Nobody's ToolKit...?

Re:There goes another one (1)

Anonymous Coward | about 9 months ago | (#45168525)

Gnome ToolKit?

Re:There goes another one (0)

Anonymous Coward | about 9 months ago | (#45168621)

This is actually a very insightful remark.

Re:There goes another one (0)

Anonymous Coward | about 9 months ago | (#45168779)

No, I think it'll end up as MTK (Miguel de Icaza's Toolkit) as I doubt he'll move to QT ... ever. Which is for the best, really.

Re:There goes another one (2)

binarylarry (1338699) | about 9 months ago | (#45168907)

He'll switch when Microsoft does.

Re:There goes another one (0)

Anonymous Coward | about 9 months ago | (#45168951)

You do realize that:

1) Miguel has nothing to do with GTK?
2) Miguel left the Gnome project years ago?

Re:There goes another one (0)

Anonymous Coward | about 9 months ago | (#45176505)

Gnobody's ToolKit.

Re:There goes another one (1)

geminidomino (614729) | about 9 months ago | (#45168299)

Not the guy who said it originally, but I think that would be the lion's share of the hilarity he mentioned.

Re:There goes another one (0)

Anonymous Coward | about 9 months ago | (#45168467)

GNU's Not Unix Image Manipulation Program Tool Kit.

Re:There goes another one (0)

Anonymous Coward | about 9 months ago | (#45168481)

no, but the toolkit is the GIMP ToolKit.

Re:There goes another one (1)

dbIII (701233) | about 9 months ago | (#45171153)

That was my feeling in the early days of gnome when their fuckups meant that gimp would no longer compile. They did improve.

Is gnome loosing? (-1)

Anonymous Coward | about 9 months ago | (#45167559)

I feel like GNOME is loosing pace. Either by forking like Mate Cinnamon or by new concurrent like Unity.

Re:Is gnome loosing? (2)

barlevg (2111272) | about 9 months ago | (#45167639)

What exactly are you concerned about them loosing [google.com] ? Maybe some horrible monster they've been keeping in their basement? Or a bio-genetic plague?

Re:Is gnome loosing? (1)

RabidReindeer (2625839) | about 9 months ago | (#45168033)

What exactly are you concerned about them loosing [google.com] ? 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?

Re:Is gnome loosing? (0)

Anonymous Coward | about 9 months ago | (#45168491)

Why can't you just tow the line and give him free reign? It passed the spell checker, isn't that all that counts?

I think you meant "toe the line". The expression comes from crew members on old wooden ships lining up for inspection by all putting the feet on the same board.

Or were you grammar trolling?

Re:Is gnome loosing? (0)

Anonymous Coward | about 9 months ago | (#45168815)

Why can't you just tow the line and give him free reign? It passed the spell checker, isn't that all that counts?

I think you meant "toe the line". The expression comes from crew members on old wooden ships lining up for inspection by all putting the feet on the same board.

Or were you grammar trolling?

It was a fail of a grammar troll. It should have read: "Why can't ewe just tow the line and give him free rain? It past the spell checker, isn't that awl that counts?"

Re:Is gnome loosing? (1)

psmears (629712) | about 9 months ago | (#45169375)

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?

Re:Is gnome loosing? (0)

Anonymous Coward | about 9 months ago | (#45168915)

The second sentence should have clued you in to the point of the first, but since you missed the other deliberate error it was obviously wasted.

Re:Is gnome loosing? (1)

MightyYar (622222) | about 9 months ago | (#45168205)

Not... a... typographical error!!!

Re:Is gnome loosing? (1)

geminidomino (614729) | about 9 months ago | (#45168501)

Worse. Much worse.

More code.

Re:Is gnome loosing? (1)

mrchaotica (681592) | about 9 months ago | (#45169671)

A Beowulf cluster of grammar Nazis!

Re:Is gnome loosing? (1)

kpsimm (528853) | about 9 months ago | (#45167641)

loosing? really?

Re:Is gnome loosing? (1)

K. S. Kyosuke (729550) | about 9 months ago | (#45168115)

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. :-)

Props to all sticking it out and trying Qt out! (4, Insightful)

Dino (9081) | about 9 months ago | (#45167769)

This is a big win for the Qt ecosystem. Between KDE libraries reworked into portable Qt modules [slashdot.org] and official iOS and Android support [slashdot.org] even with support from Digia [slashdot.org] -- Qt is gaining momentum. They even managed to survive being gobbled by Nokia [slashdot.org] , then being sold [slashdot.org] to Digia [slashdot.org] -- 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 :-)

Re:Props to all sticking it out and trying Qt out! (2)

TopherC (412335) | about 9 months ago | (#45168007)

You're running Kubuntu 13.10? How is it so far?

I've long enjoyed KDE and pyqt programming. It's nice to see the underlying library move forward so successfully. I've found that, at least with pyqt, the QT libraries are rather large to ship around. I hope this doesn't increase the size of wireshark too much. It's nice to be able to easily install and run it on platforms like raspbian.

Re:Props to all sticking it out and trying Qt out! (1)

Dimwit (36756) | about 9 months ago | (#45168133)

Someone really needs to explain the appeal of Kubuntu and KDE to me. I just don't get it. It's so *busy*: everything is huge with glowing drop shadows and spinning cursors and animations everywhere. It's also the only desktop environment I've ever sat down at that I couldn't just use immediately - I tried "creating an activity" and was left with a completely blank desktop, not even any panels or anything. There may have been keyboard shortcuts to get out of that situation, but I didn't know them and shouldn't have had to. I tried creating another activity later and the session segfaulted. This was a release version, not a beta or something.

I really want to like KDE, truly. I used KDE on FreeBSD for years, but eventually moved over to CDE on Solaris and then GNOME on Linux. I tried going back to KDE with Kubuntu 13.04 and had the above experience. So someone, please explain what KDE offers that I don't get through GNOME, Unity, XFCE, or Razor...

Re:Props to all sticking it out and trying Qt out! (1)

Dino (9081) | about 9 months ago | (#45168441)

Activities are just workspaces. They might offer a little more customization than a workspace-- but that's all they are.

I used XFCE for many years on this same machine-- without compliant. What I liked about KDE is that it ran as well as XFCE and came with everything I needed for Qt development. Also I don't need to double-load application frameworks. Iv'e been able to use KDE or pure Qt apps for everything I need.

As for drop-shadows, bouncy cursors and business-- that's both accepted and came be done tastefully. (**Cough** Unity **Cough) Like any environment, customization is both available and desirable. IMHO it was easier for me to get KDE where I wanted then Unity or XFCE

Re:Props to all sticking it out and trying Qt out! (0)

Anonymous Coward | about 9 months ago | (#45172341)

IMHO it was easier for me to get KDE where I wanted then Unity or XFCE

Do you have to do KDE first? :-)

Re:Props to all sticking it out and trying Qt out! (1)

countach74 (2484150) | about 9 months ago | (#45169221)

Haha yeah those glowing drop shadows are hideous. Thank goodness we're not stuck with them. The great thing about KDE is it's extremely customizable and actually rather performant, considering how all-encompassing it is.

Re:Props to all sticking it out and trying Qt out! (0)

Anonymous Coward | about 9 months ago | (#45170889)

KDE gives you the *only* fully and truly integrated and cohesive desktop environment out there. Neither GNOME nor Windows can hold a candle to it, or even a match.

It does also give you a set of hideous defaults - blue glow, seriously? - which you spend 15 minutes of untangling the first time you set up your desktop. Then you forget all about it. I haven't touched my settings for years.

Re:Props to all sticking it out and trying Qt out! (1)

richlv (778496) | about 9 months ago | (#45171597)

Someone really needs to explain the appeal of Kubuntu and KDE to me. I just don't get it. It's so *busy*: everything is huge with glowing drop shadows and spinning cursors and animations everywhere.

hmm. i stare at the animations a couple of days after my first install, then disable them all :)

It's also the only desktop environment I've ever sat down at that I couldn't just use immediately - I tried "creating an activity" and was left with a completely blank desktop, not even any panels or anything. There may have been keyboard shortcuts to get out of that situation, but I didn't know them and shouldn't have had to.

i'll admit that as a kde user since kde 2 (and it being my primary platform since kde 3.0), i do not use activities. i kinda understand the concept, but don't fully embrace it. the great thing is that i don't have to use them ;)

Re:Props to all sticking it out and trying Qt out! (0)

Anonymous Coward | about 9 months ago | (#45173191)

You are either stupid or lying. When you create a new activity you get a blank workspace, but if you click the icon in the upper right corner of the workspace you will get a menu for customizing the new workspace. Or, you can just right click and get a menu as well. Tell me you didn't try to right click or that you couldn't see the icon in the upper right corner? The icon in the upper right corner's default is to have the words "New Activity" on it.
 
Your comment doesn't demonstrate anything about KDE, just that you are a moron.

Re:Props to all sticking it out and trying Qt out! (1)

game kid (805301) | about 9 months ago | (#45170559)

It's probably due in part to the whole KDE Free Qt [kde.org] thing. It keeps Qt free in the event Qt isn't...um...kept free. It's pretty nice.

GTK+ is ugly. (3, Insightful)

Anonymous Coward | about 9 months ago | (#45167817)

There you go, "Gnome" with all your bullshit misunderstanding of how a GUI is intended to look like. Go Qt!

Not now. But soon, soon... (0)

Anonymous Coward | about 9 months ago | (#45167863)

Now it only takes Inkscape and GIMP to follow.

Re:Not now. But soon, soon... (0)

Anonymous Coward | about 9 months ago | (#45168213)

I don't know how krita compares to gimp these days, but it showed some promise when I looked a year or two ago. Karbon might also be closing in on Inkscape, but I think it's a bit further off.

Re:Not now. But soon, soon... (0)

Anonymous Coward | about 9 months ago | (#45169265)

Krita isn't supposed to fill the same use cases as Gimp.

Gimp is an all-purpose image manipulation program.
Krita is designed for digital painting.

Gnome tool kit (4, Insightful)

caseih (160668) | about 9 months ago | (#45168095)

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.

Re:Gnome tool kit (1)

kthreadd (1558445) | about 9 months ago | (#45168641)

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.

They did? I still receive email to gtk-list.

Re:Gnome tool kit (1)

caseih (160668) | about 9 months ago | (#45172533)

That's true. gtk-list is still gtk-list@gnome.org, but my e-mail client shows "Gnome list" as the long name.

Re:Gnome tool kit (2)

Darinbob (1142669) | about 9 months ago | (#45168901)

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?

Re:Gnome tool kit (1)

Guy Harris (3803) | about 9 months ago | (#45169419)

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?

It will make it an app that doesn't use X11 on OS X.

It won't make it an all-Cocoa app (although it will, modulo issues with QtMacExtras, use the native toolbar widget, at least, and, time permitting, it'll use the native file dialog sheets rather than the definitely-doesn't-look-like-OS-X Qt file dialog).

It won't be sufficient to make it an app following the OS X "one process for all open windows" model; that would require, for example, replacing all the static variables holding dissection state with per-open-file variables (doable, but a fair bit of work). Whether that will be done for 1.12 is another question.

Re:Gnome tool kit (1)

caseih (160668) | about 9 months ago | (#45172493)

Yes Qt will make it a non-X11, more native application on OS X (carbon, though if I recall correctly).

Re:Gnome tool kit (1)

Guy Harris (3803) | about 9 months ago | (#45173017)

Yes Qt will make it a non-X11, more native application on OS X (carbon, though if I recall correctly).

Newer versions of Qt support 64-bit programs, so they don't run atop Carbon.

Re: Wireshark runs without X11 under MacOSX (1)

datalife (17290) | about 9 months ago | (#45179877)

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

WINGs (1)

turgid (580780) | about 9 months ago | (#45168505)

I'd like to see it ported to WINGs [wikipedia.org] . It's simple, fast, pretty and not married to C++.

Re:WINGs (0)

Anonymous Coward | about 9 months ago | (#45172003)

Good idea. WINGs is one of the best GUI toolkits I've ever used. Sony is using it for their next-gen phone OS. I've been using the beta for a couple months and it's fucking awesome. It makes Android and iOS 7 look like outdated shit.

rewrite code (0)

Anonymous Coward | about 9 months ago | (#45168921)

kinda off topic but: i actually don't mind rewriting or converting lots of code. I find that writing code is fun. but that is just me.

Status of QT? (1)

Anonymous Coward | about 9 months ago | (#45169341)

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.

Re:Status of QT? (3, Insightful)

Guy Harris (3803) | about 9 months ago | (#45169525)

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.

Fortunately, yes, you are wrong. Digia bought the business side of Qt from Nokia in 2012 [digia.com] . The free-software side of Qt is the Qt Project [qt-project.org] .

Re:Status of QT? (2)

richlv (778496) | about 9 months ago | (#45171609)

i met digia guys in tallinn last year at akademy (kde conference), they gave me a free t-shirt. seemed nice =)

Re:Status of QT? (0)

Anonymous Coward | about 9 months ago | (#45169623)

Nokia sold Qt to Digia over a year ago. If you would read Slashdot [slashdot.org] , you'd know that..

Re:Status of QT? (0)

Anonymous Coward | about 9 months ago | (#45171371)

Nokia bought QuickTime? Since when?

Wireshark [chown] sucks (0)

Anonymous Coward | about 9 months ago | (#45170465)

I don't use software that chmods or chown mydirectories. Wireshark has done so. Citation? Look it up. Wireshark sucks.

Re:Wireshark [chown] sucks (1)

Guy Harris (3803) | about 9 months ago | (#45171105)

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.

Re:Wireshark [chown] sucks (1)

deviated_prevert (1146403) | about 9 months ago | (#45173245)

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.

Re:Wireshark [chown] sucks (1)

Guy Harris (3803) | about 9 months ago | (#45175937)

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 [wireshark.org] :

WIRESHARK CONTAINS OVER TWO MILLION LINES OF SOURCE CODE. DO NOT RUN THEM AS ROOT.

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 [wireshark.org] , 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 [tcpdump.org] (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?

Re:Wireshark [chown] sucks (1)

deviated_prevert (1146403) | about 9 months ago | (#45177143)

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 [wireshark.org] :

WIRESHARK CONTAINS OVER TWO MILLION LINES OF SOURCE CODE. DO NOT RUN THEM AS ROOT.

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 [wireshark.org] , 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 [tcpdump.org] (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.

Re:Wireshark [chown] sucks (1)

NotBorg (829820) | about 9 months ago | (#45185555)

Wireshark isn't for crybabies anyway.

great improvement (0)

Anonymous Coward | about 9 months ago | (#45170587)

gtk v qt politics aside, really like the design choices in the development qt build. hated having to search for where to enter capture filters.

GTK+ community is declining (2)

jcdr (178250) | about 9 months ago | (#45170703)

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.

Re:GTK+ community is declining (1)

Desler (1608317) | about 9 months ago | (#45171387)

The only thing Nokia changed was adding an LGPL option. It was already dual licensed under the GPL.

Re:GTK+ community is declining (1)

jcdr (178250) | about 9 months ago | (#45173601)

LGPL vs GPL was the key point for non-free projects that instead was forced to use the commercial license.

Re:GTK+ community is declining (0)

Anonymous Coward | about 9 months ago | (#45171623)

GTK+ was outrageously superior to anything out there about 5 years ago

GTK has always been a GUI kit. Qt has always been a complete library of which GUIs are just one part. Qt is like the Java standard library for C++.

The only thing GTK+ has done "better" was that Qt was GPL/commercial whereas GTK+ was always LGPL.

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.

Qt has been GPL since 2001.

GTK+ is rigidly C based, Qt is rigidly C++ based. That will not work.

Re:GTK+ community is declining (1)

jcdr (178250) | about 9 months ago | (#45173643)

I should have used the Gnome libraries dependencies instead of GTK+ to compare to the Qt complete library.

The GPL license was a showstopper for non-open projects that don't wants to use a commercial license. The LGPL changed that important nuance.

The difference in the language is certainly a massive concern in case of a direct merge, but I don't think there is any features of one of the project that cannot be implemented in the language used by the other project. This is still a hug amount of work...

A other even more ideal dream, C and C++ should also merge. Each new standard tend to share the best feature of the other, but this process is depressingly slow, and the C++ name mangling fiasco that make each compilers incompatible is still not even in the radar of the foreseeable next C++ standards.

Massive loss of manhours... (0)

Anonymous Coward | about 9 months ago | (#45172019)

The whole GTK/Qt rivalry reeks of agent provocateur.

KDE was rapidly becoming a desktop to rival Windows.

But then a shit storm was raised about the license of the underlying Qt library.

And at the center of that shit storm you find a guy that goes on to implement one MS concept after another into GTK/Gnome.

Or as the saying goes, Divide and Conqueror.

Intrusion detection (1)

Ralph Ostrander (2846785) | about 9 months ago | (#45173049)

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?
Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?
or Connect with...

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>