Linked by Thom Holwerda on Sat 22nd May 2010 21:18 UTC
Permalink for comment 426161
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2008-07-15
I don't know where you're located, but in a lot of the US there are a hell of a lot of unsecured networks. Most of the time they're put there by the cable or DSL providers and the home users never touch them. The worst of it is, when I tell them they should secure it, they always ask "why?".
Personally, I'm of the belief that if you don't care enough to lock down your network you deserve to get sniffed. You're asking for it. If it's a deliberately public Wifi hotspot, then know that you are wide open and can be sniffed and accept the fact.
I agree with the rest of your points. Wow, Google might've accidentally seen someone's twitter postings. Big deal. The really important stuff is locked behind SSL anyway. Still, I don't see any harm in investigating it. I think, in this case, this was probably an honest error, but by all means look into it. It's a pity the governments seem to be doing their job in this case but some of them (US) don't do crap when it comes to real violent crime.