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.
Wireshark is far from being an egghead tool that only professionals might use. It's also useful for running aircrack-ng. I'm happy they've finally reached 1.0.
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/
I wish I could sniff on multiple interfaces.
Or exclude specific interfaces from the pseudo-device available in some versions (like my linux copy)
Or filter out duplicate packets (not retransmissions, but the literal same packet: I bridged two interfaces, and the pseudo-device captures both the bridge and the bridge member)
Or just add localhost to a bridge.. why I can't do this is outside my understanding (until someone gives a crafty answer)
Or even just route all traffic destined for localhost through a physical interface first (I just want to capture all my packets, including localhost and a bridge with several ethernet members, but only once!)
Ah, it's on the wishlist. For another day, perhaps...
slashdot: where everyone yells sarcastic metaphors to themselves to understand the issue
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
I do a lot of Biztalk dev and I often need to send data to remote HTTP locations. Usually the outgoing message is transformed inside an outgoing pipeline and it is not always easy to see exactly what is being sent to the client. This is where WireShark has come in handy. I just monitor my ethernet interface for a few seconds. The results are usually colour coded and easy to read. Very useful tool.
http://projectleader.wordpress.com
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.
http://wireshark.zing.org/download/osx/Wireshark%201.0.0%20Intel.dmg
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?
I have a 'black box' on my home network. It's a voip phone, provided by our local telecom, and I'd really like to see what traffic it's sending to and receiving from the outside.
I've scanned it with nmap and not found any open ports from the outside. It's sitting behind a nat router, and the company won't tell me which ports it would need to forwarded (though somehow it's still able to receive calls and messages from the outside).
Actually, the company says I should forward ports 20000-60000 (seriously), but I think I won't do that.
I'm really curious to see the traffic it sends and receives, and also whether it's using any encryption. Is it possible to use Wireshark to sniff the traffic from another box that is within the same LAN, and where might one find a good tutorial for such a project?
Gnome: A never ending quest to make unix friendly to people who don't want unix and excruciating for those that do.
Adobe: v1.0 is released; a week later 1.0.1 is released. A few months after that, 1.0.2. Then three years go by, and suddenly it's at 2.0, which is broken from the install.
Microsoft: v1.0 is released; no one buys it. v2.0 is released; it's still not really usable. v3.0 comes out, and people suddenly line up for it around the block. v3.0SP1 is released and fixes most of the really bad bugs while introducing a few others, some random security vulnerabilities, invalidating half the licenses of all previous versions, and causes DrDOS to crash.
Apple: v1.0 is released, but it has a bug so Apple pulls it from the download server for a few hours, after which a patched version replaces it, with the same exact version number, and no mention of any bugfix in the release notes. Any mention of any alleged switcheroo or the problem that existed in the first 1.0 release is ruthlessly and systematically quashed in the support forums on Apple's website; unfortunately, their lawyers can't censor the entire net.
You see? You see? Your stupid minds! Stupid! Stupid!
It's easy to simulate. Just login to a remote system via VNC/RDP and then run Wireshark on it. Remove any filters that Wireshark might automatically add to save you from yourself. You can also recreate this with SSH and tcpdump.
I would make sure that it's not a very important remote system though.
One of the most useful features of wireshark is its breakdown of (known) protocols. It makes it a lot easier to follow a DHCP address acquisition or a DNS request and to dig into the individual flags of said DNS request (was it an update? did it have any prerequisites?)
However, probably the best use I've found for Wireshark was troubleshooting VoIP with SIP and RTP. Wireshark has great plugins for visually laying out each step of the SIP conversation, including showing you where the RTP stream initidated at. If you've ever tried to troubleshoot SIP via a NAT setup with various proxies like SER throughout, it's an invaluable tool. It'll even graph jitter for you. Just tcpdump to an output file and load it up in Wireshark.