Re: [Nolug] Unsecured wireless networks with everybody's favorite OS

From: Brad Bendily <bendily_at_gmail.com>
Date: Wed, 29 Jul 2009 16:10:38 -0500
Message-ID: <e27c898e0907291410yca208fbva552cf49f286ecef@mail.gmail.com>

What? Go talk to the guy? Are you crazy? That's not how we handle
disputes in this country buddy.
Here we'll pass a law that will require him to register his device,
then he'll have to get approval for each person to
use the service. But before each person can use the service, they'll
have to attend a training class that will
show them all the do's and don'ts.

And since your clients aren't registered to use his device, they
won't/can't/shouldn't connect and use it, it will
be against and unenforceable law!

On Wed, Jul 29, 2009 at 4:05 PM, -ray<ray@ops.selu.edu> wrote:
>
> Here's a crazy idea.  Go ask the neighbor to secure his access point. Tell
> him it's a hazard to your business as well as his own.   If he refuses,
> setup a sniffer and send disassociation packets everytime you see a new MAC
> on the network.
>
> Unless he's a coffee shop?  Then offer to turn off your sniffer in exchange
> for free coffee :)
>
> ray
>
> On Wed, 29 Jul 2009, Chris Jones wrote:
>
>> I have an issue with a client, I was wondering if any of you have ran
>> into this before, and if you know of any way to prevent it.  I've done
>> a ton of research, and have gotten nowhere.
>>
>> My client has a secure internet connection.  A lot of their employees
>> have laptops.  They have a filtering device that blocks viruses,
>> spyware, spam, etc from getting into their LAN, plus it blocks the
>> users from accessing inappropriate sites from work.
>>
>> The problem is they have a neighbor with a wide open wireless AP, so
>> the employees just get on that and can then do whatever they want.
>> I'm not sure if they're doing it intentionally, or it could just be
>> Stupid Windows (TM) being insistant on connecting to SOMETHING.  The
>> fact that they can spend all day on myspace or looking at porn is the
>> minor issue, the major issue being that it is an opening for malware
>> to come into their network, not to mention that it's possible for a PC
>> to route traffic between its WAN and LAN ports, so it could possibly
>> become a security issue as well.
>>
>>> From what I can see, there's absolutely no way to do it, which is
>>
>> insane.  Windows has a group policy that can block acess to ad hoc
>> networks, but that's about as far as it goes.  Apparently MS believes
>> that an AP is far more secure than an ad hoc network.
>> ___________________
>> Nolug mailing list
>> nolug@nolug.org
>>
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Ray DeJean                                       http://www.r-a-y.org
> Systems Engineer                    Southeastern Louisiana University
> IBM Certified Specialist              AIX Administration, AIX Support
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
> ___________________
> Nolug mailing list
> nolug@nolug.org
>

-- 
Have Mercy & Say Yeah
___________________
Nolug mailing list
nolug@nolug.org
Received on 07/29/09

This archive was generated by hypermail 2.2.0 : 08/06/09 EDT