All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: Allowing access only some sites - onely some mac address
Date: Tue, 30 Aug 2005 12:22:46 -0500	[thread overview]
Message-ID: <431495E6.30205@riverviewtech.net> (raw)
In-Reply-To: <E656E2CC1C5AEB42ACB00EB83122C7741FD017@farmer.vikus.com>

> You may also want to consider getting arpwatch. arpwatch will tell you when a particular user changes their MAC address. MAC spoofing, while more difficult than IP spoofing, is still fairly trivial and particularly in this case where you are using a "blacklist" approach for filtering MACs. So if I'm the one with MAC 00:D8:02:D8:C8:DF and I want to get around your rules, I'll get a utility to change my MAC to something that won't trigger your firewall rule, like 10:D8:02:D8:C8:DF, which I can be sure won't collide with another MAC for quite some time.
> 
> If the particular users you are trying to filter for aren't very technical then I wouldn't worry but after two years of being a lab assistant/server admin for a network security class I tend to be a little paranoid. =)

You are absolutely correct.  So my immediate response to this is do the exact opposite, have the MAC of the computers that are allowed to access any thing other than the sites in question.  As far as needing ARP watch to look for changes in IP, you could watch for the MAC and IP pair of allowed systems.  Sure people could still get around this but they will be breaking other things too.



Grant. . . .


  reply	other threads:[~2005-08-30 17:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 13:39 Allowing access only some sites - onely some mac address Derick Anderson
2005-08-30 17:22 ` Taylor, Grant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-30 20:10 Derick Anderson
2005-08-30 14:44 Derick Anderson
2005-08-29 19:41 Sebastião Antônio Campos (GWA)
2005-08-29 19:49 ` Sp0oKeR
2005-08-29 20:02   ` Damon Gray
2005-08-29 20:07     ` Sp0oKeR
2005-08-30  2:27 ` Grant Taylor
2005-08-30 13:49 ` Jiann-Ming Su

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=431495E6.30205@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=netfilter@lists.netfilter.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.