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.

In reply to Re: Re: Re: Re: Secure Perlmonks by SyN/AcK
in thread Secure Perlmonks by Mirage

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.