All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Topher Fischer <javert42@cs.byu.edu>
Cc: netdev@vger.kernel.org
Subject: Re: ARP Spoofing
Date: Wed, 02 May 2007 14:55:53 -0400	[thread overview]
Message-ID: <4638DEB9.90608@hp.com> (raw)
In-Reply-To: <4638CDED.4020100@cs.byu.edu>

Topher Fischer wrote:
> Does the kernel have any protection against ARP spoofing?  If not, does
> anybody know why not? (As in, nobody has done anything, or because of A,
> B, and C).
> 
> Thanks,
> 

If by arp spoofing you mean receiving arp replies from multiple sources and
trusting all of them, then I haven't seen anything.  I speaking from
experience as having been bitten by this in earlier kernels (2.6.15 and 2.6.17),
it's a pita to diagnose in a large environment.

I don't know the history as to why nothing has has been done.

-vlad


  reply	other threads:[~2007-05-02 18:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 17:44 ARP Spoofing Topher Fischer
2007-05-02 18:55 ` Vlad Yasevich [this message]
2007-05-02 20:39   ` Chris Friesen
2007-05-02 20:45     ` Vlad Yasevich
2007-05-02 23:45     ` Topher Fischer
2007-05-03  0:16       ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4638DEB9.90608@hp.com \
    --to=vladislav.yasevich@hp.com \
    --cc=javert42@cs.byu.edu \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.