War Driving To Be Protected In NH
AllMightyPaul writes "A big article on Wired.com talks about the new House Bill 495 that would legalize the innocent stumbling upon open wireless networks. Basically, it put the burden of securing a wireless network on the owner of the network and allows people to connect to open networks that they believe are supposed to be open. This is excellent news as I'm sure we've all tried to connect to one wireless network and ended up accidentally connecting to another one. Being from NH, now I can finally drive through Manchester and connect anywhere I want with little worry, but not until after January 2004, and that's if the bill passes the Senate."
So was it previously illegal? AKAIK, there are no laws against war driving, so while they may have protected this right, they didn't legalize it. Definately a step in the right direction, though.. it's so infrequent that we see lawmakers making laws to PROTECT our freedoms rather than remove them.
Everyone is entitled to their own opinion. It's just that yours is stupid.
There are still real moral issues here with whether or not it's actually RIGHT to connect to other people's networks. Just because the networks are not completely secure, you're still not justified in connecting to them, specifically if your reason to connect is to abuse them.
The law has decent motivation, but it's basically saying "Go ahead and break into wireless networks, because if they're not completely secure, it's not your fault." What happens when people start snooping the traffic, stealing corporate secrets, and then claim that the wireless network wasn't secure, so they can't be responsible?
Mooniacs for iOS and Android
Well, I don't know about you, but here in NC if I drive through a nearby office park with Kismet there's a spot with EIGHT IDENTICAL members of the "linksys public access network" if you know what I mean (LinkSys products with default unprotected configs).
... you might just be committing a crime and theft of service if you pick the wrong one.
.. how about just renaming your access point to "PRIVATE ACCESS" or something that takes half a brain cell)....
:-)
.. how do you KNOW we have a wireless network ... from OUTSIDE??? You must be a TERRORIST!"
If I were to hypothetically sniff some of these packets, I might hypothetically discover that they are going to different ISPs, which makes me hypothetically believe that most if not all of these belong to different companies.
So imagine you are an employee of one of these companies and the boss tells you "hook up to the linksys"
This law puts the burden on the hardware owner to make the fucking tiniest effort (I'm not talking IPsec or even turning on WEP
This is GOOD, not BAD.
The signal is physically going through my body and if it doesn't say "Don't Use Me", then by fuck, I'm going to use it! I figure that's in exchange for the 0.00001% increased cancer risk.
I debated going into these businesses and telling them that I'm a computer security professional and would be happy to give them some free consulting but then I decided at least one of them would get panicky and have me arrested. "But
No good deed goes unpunished you know.
I'll summarize it again as I have in other forums.
- My laptop sees a signal and requests access to the network by asking for a DHCP address.
- Access point sees my request and GRANTS me a lease on an IP address with which I can access their network
- I surf using the network
- I leave.
I asked, they said YES. They could have easily denied me, but they invited me into the network when I asked if I could. There are SO MANY different ways to keep people out, that owners of AP's just have to do something to secure themselves. Shame on them if they fail to do that.
-- There is no sig line, only Zuul.