[kismac] Re: connecting to networks

  • From: "Barry Woods" <barry99705@xxxxxxxxx>
  • To: kismac@xxxxxxxxxxxxx
  • Date: Fri, 5 May 2006 21:54:55 -0800

Just to throw some laws in the mix... And a rough explanation.
The federal law, I.E. all 50 states. http://www.usdoj.gov/criminal/cybercrime/1030_new.html

Rough translation, So, let's say we just want to do some Internet surfing via a wide-open, unencrypted AP of unknown origin (probably a neighbor), from the luxury of the living room

-Is it intentional? YES.
-Is it a "computer" I'm accessing? According to USC 18 - YES. An AP is a
computer by definition.
-Is it a *protected* computer? According to the definition in USC 18 - Not
inherently. But in this case we'll be getting on the Internet, so YES.
-Is the access *authorized*? It's kind of subjective, but I don't believe
-Am I causing a loss of $5000 or more? Easily - See below.

"Loss" can include things like time spent responding to the incident, damage
assessment, etc. So, "loss" can add up pretty quickly with these
intangibles. However, it doesn't count unless the loss was incurred as a
result of a crime.

So, to sum up - Chilling in your living room and surfing via your neighbors
AP (as harmless as it seems) is a federal crime. Also, some states like
Alaska now have laws that specifically prohibit doing this as well (Theft of

On 5/1/06, Kharlyt <Kharlyt@xxxxxxxxxxxx> wrote:

That's probably what it's about 'cause the network I think about isn't SSID hidden... thank you both for your explanations. Le 1 mai 06 à 11:59, themacuser a écrit :

> Also, the network may have a higher power base station than your
> airport card - you can hear it in passive mode, but your airport
> card isn't transmitting strongly enough for it to pick you up.
> On 01/05/2006, at 6:50 PM, Robin L Darroch wrote:
>> The networks you see in your Airport menu are those which are
>> broadcasting their network name (or "SSID").  However, for added
>> security (although only a bit of added security), some people turn
>> off SSID broadcast on networks.  To connect to such a network, you
>> need to choose "Other..." from the Airport network, then type in
>> the SSID.  KisMAC can often identify the SSID of networks which do
>> not broadcast them.  However, getting the SSID is only one-third
>> of the battle.
>> You also need to know the network key if the network is encrypted
>> (i.e. if it has "WEP", "WPA", "LEAP" or anything other than "NO"
>> in the Encryption column in KisMAC (unencrypted networks show up
>> as green dots on the map).
>> Finally, the network administrator may have a list of network
>> adapter hardware addresses (or "MAC addresses") which are allowed
>> to connect to the network.  If this is the case, either your
>> adapter's MAC address needs to be on the approved list, or you
>> need to fake your MAC address (which, while possible, is not an
>> easy thing to do).
>> In general, if a network hides its SSID and/or uses encryption and/
>> or has a MAC address access list, it's because the administrator
>> doesn't want you to connect to it... and attempting to do so
>> (often even if that attempt is unsuccessful) could be a criminal
>> offence.  In fact, it's just as much of an offence to connect to
>> an open network that broadcasts its SSID if you do so without
>> permission, but you can always use the "oh, my computer did it all
>> by itself" excuse in that case.
>> Cheers,
>> Robin
>>>     Hi,
>>> I am using Kismac sometimes with my airport express card,
>>> sometimes with my dwl-122 and I realize that a lot of networks
>>> that are seen in KisMAC are not seen once it is quit and that I
>>> look at the networks found with my airport card alone, and so it
>>> is not possible to connect to those and use them.  Is there a way
>>> to connect to these ?  'cause I suppose if it can be seen, it
>>> should be possible to connect to it in a way or the other...
>>> Thanks.
>> --
>> ---------------------------------------------------------------------
>> ----
>>  Robin L. Darroch - PO Box 2715, South Hedland WA 6722 - +61 421
>> 503 966
>>       robin@xxxxxxxxxxxxx - robin@xxxxxxxxxxx - robin@xxxxxxxxxxxxx

Other related posts: