From: Will Lotto <lotto@impulse.net.au>
To: lartc@vger.kernel.org
Subject: Re[2]: [LARTC] Fake hardware address
Date: Sun, 10 Feb 2002 02:42:48 +0000 [thread overview]
Message-ID: <marc-lartc-101330897432580@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101324744330399@msgid-missing>
Yes, they do throw up an error.
... Both cards believe the packets are destined for them. ...
basically, they'll fight :)
To take a mac address, one needs to wait for a PC to go offline (or
take a PC offline), then steal the MAC. ... Stealing the MAC is very
easy, intel network cards let you SET the MAC in windows (under
advanced settings) ... in linux, there are programs that can do it,
which work with most cards.
As for protection, I don't believe there is a simple way to
protect against such an attack ... Encryption? :)
Will
> :
>> > Helo...
>> > I need to ask about hardware address....
> if you have two cards with identical mac addresses on your network, will
> they work together? surely one will get an error?
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
---
"They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-02-10 2:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 9:28 [LARTC] Fake hardware address Adi Nugroho
2002-02-09 9:45 ` Andreas Gietl
2002-02-09 11:06 ` bert hubert
2002-02-09 13:34 ` ewan
2002-02-10 2:42 ` Will Lotto [this message]
2002-02-11 12:39 ` Ard van Breemen
-- strict thread matches above, loose matches on Subject: below --
2002-02-11 2:24 Re[2]: " Adi Nugroho
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=marc-lartc-101330897432580@msgid-missing \
--to=lotto@impulse.net.au \
--cc=lartc@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.