Re: Blacklisting methodology

Matt:
   If we are going to include banning via IP addresses, we need to make 
sure there is very clear documentation.  Personally, I don't know if 
the benefits outweigh the cost.  There are 2 non-extreme cases where 
this can backfire.
   The first is that most companies do NATing of internal IP addresses.  
Thus every employee seems to originate from the same IP address.  If we 
ban 1 person, we ban them all.  While this may seem okay, what about in 
those cases where the ISP does NATing?
   The second is that most users change IP addresses fairly often, even 
in the world of cable modems and DSLs.  If they are banned, they can 
just try tomorrow.
   I don't know how realistic this is in a world where there is not a 1 
to 1 static relationship between a person and an IP address.  Also, I 
am just playing devil's advocate.


-matthew

On Thursday, May 8, 2003, at 03:21 PM, Matthew Schmidt wrote:

> Hey guys.  I'm working on banning people from JLCP via the admin 
> console and I was wondering if anyone had a nice way of blocking IPs.  
> We can get the IP from the request as it comes in and check in our 
> database to see if its blocked.  My question is how far up do we want 
> to block.  If someone's IP is 216.27.54.20, just blocking that exact 
> address won't work for a dynamic range.  Do we need to block all the 
> way up to 216.27.*.*? or just 216.27.54.*.  Your thoughts?  We are 
> also blocking by username, but this doesn't do a whole lot of good 
> since someone could just create another user with a different > username.
>
> -Matt
>
> _______________________________________________
> JL-Volunteers mailing list
> [email protected]
> http://cato.usermagnet.com/mailman/listinfo/jl-volunteers