, SecurityFocus 2003-11-12
In a rare wireless hacking prosecution, federal officials this week accused two Michigan men of repeatedly cracking the Lowe's chain of home improvement stores' nationwide network from a 1995 Pontiac Grand Prix parked outside a suburban Detroit store.
Expand all |
Post comment
Wireless hacking bust in Michigan
2003-11-13
-=CORE=- (5 replies)
-=CORE=- (5 replies)
Wireless hacking bust in Michigan
2003-11-13
Anonymous (1 replies)
Anonymous (1 replies)
Wireless hacking bust in Michigan
2003-11-13
Anonymous (1 replies)
Anonymous (1 replies)
Wireless hacking bust in Michigan
2003-11-14
<secure72 (at) hotmail (dot) com [email concealed]> (1 replies)
<secure72 (at) hotmail (dot) com [email concealed]> (1 replies)
Wireless hacking bust in Michigan
2003-11-14
MINDeSET (1 replies)
MINDeSET (1 replies)
Wireless hacking bust in Michigan
2003-11-14
David Feligno (2 replies)
David Feligno (2 replies)
Wireless hacking bust in Michigan
2003-11-14
Anonymous (2 replies)
Anonymous (2 replies)
Wireless hacking bust in Michigan
2003-11-14
Kevin Poulsen <klp (at) securityfocus (dot) com [email concealed]>
Kevin Poulsen <klp (at) securityfocus (dot) com [email concealed]>
Wireless hacking bust in Michigan
2005-09-03
JHN (2 replies)
JHN (2 replies)

In this instance, had Lowes deployed WEP deliberate actions would have been required to circumvent the security measures (however filmsy) in order gain access to their network, which is highly illegal. Accessing the Lowes network initially probably could not be construed as a nefarious event. Lowes could opt to provide a public hotspot. However, once they started poking around the network itself (to say nothing of deploying credit card sniffing utilities), they would have crossed the line between gaining "public" access to the Internet and deliberately accessing a private network.
Shame on Lowes for letting themselves get into this mess... Even if it turns out that it was some poor local schlub who thought it might be useful for the store to be up on technology.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/articles/7438/23755#23755