From: Topher Fischer <javert42@cs.byu.edu>
To: Chris Friesen <cfriesen@nortel.com>
Cc: netdev@vger.kernel.org
Subject: Re: ARP Spoofing
Date: Wed, 02 May 2007 17:45:05 -0600 [thread overview]
Message-ID: <46392281.8040909@cs.byu.edu> (raw)
In-Reply-To: <4638F6E8.3060609@nortel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris Friesen wrote:
> Vlad Yasevich wrote:
>
>> If by arp spoofing you mean receiving arp replies from multiple
>> sources and
>> trusting all of them, then I haven't seen anything.
>>
>> I don't know the history as to why nothing has has been done.
>
> This concept is a valuable tool to allow for fast publishing of IP
> address takeover in redundant-server situations.
>
> There are ways in which it can be misused, but that doesn't make it an
> invalid technique.
I don't think it would be too difficult to preserve this kind of
functionality while improving security. Is this really the only reason
why nothing has been done to protect machines from ARP spoofing?
- --
Topher Fischer
GnuPG Fingerprint: 3597 1B8D C7A5 C5AF 2E19 EFF5 2FC3 BE99 D123 6674
javert42@cs.byu.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFGOSKBL8O+mdEjZnQRAowZAJoCawbK1IM+TxBvAaNGtzdw5UrDmgCdGB5L
1mJdu4W61Opj+zqgtQJfdp8=
=qlBs
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-05-02 23:40 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
2007-05-02 20:39 ` Chris Friesen
2007-05-02 20:45 ` Vlad Yasevich
2007-05-02 23:45 ` Topher Fischer [this message]
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=46392281.8040909@cs.byu.edu \
--to=javert42@cs.byu.edu \
--cc=cfriesen@nortel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).