Also you should consider what kind of network you are on. Say you are at work, well then its likely you're on a switched network
switched networks are no real match, as you can fake packets that will confuse the switch, so you can get all the packages you want. I think especially as a security expert you shouldn't feel all safe because its may seem hard it do - as long as it is possible there is the danger.

By the way, hackers are not people who enter into machines and try to harm others.
see here

Yes yes, I'm well aware of the difference between hackers and crackers. To me, the terms are interchangable. Its not my fault the media decided to call crackers, hackers.

I don't think that you completely understood the answer to my question. When I said

If someone is taking the time to sniff packets on your network, then you have likely got a lot more to worry about then just your perlmonks password.

I was refering to the network as say your home computer. I was trying to make the point that you should be alot more concerned with someone sniffing passwords other than just your perlmonks password, or with something potentially worse, say using your netbios shares (or any other vulnerability for that matter) to "hijack" your computer.

I agree, dsniff is a simple enough tool to use, but the point that I was trying to initially make is that you should be much more concerned about the other vulnerabilities inherent on most peoples home computers.

As for your comment about switched networks,

switched networks are no real match, as you can fake packets that will confuse the switch, so you can get all the packages you want. I think especially as a security expert you shouldn't feel all safe because its may seem hard it do - as long as it is possible there is the danger,

I think that this is an unfair statement. While it is true that there is some inherent insecurities involved with a switched network environment, it has proven to be a viable solution for may small business (as well as many large scale businesses). It again comes to my point that you should be most concerned with other things.

As a security expert, its not as important to recognize and address every single potentially exploitable hole, as it is to prioritize and address the most significant problems. I was merely trying to show that there are other things to be more concerned about. ARP poisoning, while definitely not to be taken lightly, is not as dangerous as some of the other hacks, or "cracks" (whatever), that take much less skill to accomplish.

Yes yes, I'm well aware of the difference between hackers and crackers. To me, the terms are interchangable. Its not my fault the media decided to call crackers, hackers.
Ok, sorry for misunderstanding you.

I was refering to the network as say your home computer. I was trying to make the point that you should be alot more concerned with someone sniffing passwords other than just your perlmonks password, or with something potentially worse, say using your netbios shares (or any other vulnerability for that matter) to "hijack" your computer.


The point is, that I often use my notebook from other networks(with wireless lan, so no switching) where I don't know everyone. I do know that most of these people there are able to use techniques to get any information that may give some fun, such as account information. I already use other means such as pop3s (and I don't have open netbios shares...) to minimize open vulnerabilities, and I wondered if it was possible to do so with perlmonks.