Slashdot Mirror
Wireshark 1.0 Released
katterjohn writes "After almost 10 years of work, Wireshark 1.0 has been released. Wireshark is the award-winning protocol analyzer, formerly known as Ethereal. The release features several security fixes and an experimental package for Max OS X Intel."
would this still be illegal in Germany?
The higher the technology, the sharper that two-edged sword.
Whenever some product claims to be "award-winning", I always wonder what that award is. It's like the word "professional", that also lost its meaning. So, anybody have any pointers to any kind of "award"?
Now come on! What sort of a lede is that? Just a tease and no candy? What does Wireshark 1.0 DO for pete's sake?
I'll be off to update mine today. It's the best improvement on tcpdump I've ever used.
In other news, astrophysicists have announced that they now know what all that dark matter is: it's stupidity.
The site is slow at the moment, if you want to download the thing, skip the chase and go straight to http://sourceforge.net/projects/wireshark/
those features will be available in Wireshark 2.0, forecast for release in 2018 at their current pace
This project took 10 years of continuous development and public testing to reach a 1.0 release. This timeframe is not atypical; F/OSS 1.0 releases are usually stable, reliable, and heavily featured. Some projects never make a 2.0 release, instead making point releases on top of 1.0 indefinately.
The 1.0 release of most commercial software comes after extremely limited public testing, and the developers scramble to make a 2.0 release within a year. Commercial 1.0 releases are frequently buggy and have obvious gaps in functionality, which are often not completely addressed in 2.0.
wireshark-setup-1.0.0.exe
And aircrack-ng is far from an egghead tool. It's useful for... wait a minute....
A dev after my own heart! I use it to capture ASP.NET web service requests as it's far easier to deal with than WSE3 tracing or serializing objects before passing them to the web proxy (which usually leaves you without namespaces anyway).
Over the years, I've found protocol analyzers to be indispensable for developing and debugging modern MS-based network apps. They hide so damned much from the developers these days, often times it's the only way to see what's really going on.
It goes from God, to Jerry, to me.
Long story short: I had a SQL client app that tried to connect to the SQL server with a hard-coded password. I needed to know the password to set on the server. Fired up wireshark, found the password, set said password on the server, and it was a go.
:Or just add localhost to a bridge.. why I can't do this is outside my understanding (until someone gives a crafty answer)
It's a simple reason. Bridging is a layer 2 technology, as IP is layer 3. As I expected, a "localhost" on Linux does not have a MAC address (required for layer 2).
Man, people have mod points burning holes in their keyboards tonight.
I fail to see anything at all "interesting in this". Taking advantage of other people because you are more knowledgeable than them, breaking the law, and then boasting about it on Slashdot is -5 Lame, especially when the level of expertise involved is what is usually ascribed to "script kiddies".
And no, you don't get a pass because it was the "only black hat thing I've ever done", like we believe that, and it sure sounds like the entire objective of your weak excuse for "black hat" action was to sniff their traffic, since changing their router setup was hardly necessary if you just wanted to steal access.
Maybe I'm just having an old man moment, but I kept expecting some kind of punch line in there, and it ended up just being "my neighbor left his garage door open, and I stole a six-pack out of his fridge". WTF is that about?