broadcast | madrock

A few years back, some friends and I were messing around with a Taco Bellâ€™s drive-thru frequencies. RijilV and isotek showed me how easy it was to hijack the frequencies of just about any fast food restaurant with a very simple mod to a ham radio. The radios they used were Yaesu VX-5 and VX-7 models. We had a few weeks of occasional fun, sitting a few parking lots away and saying all kinds of horrible things to potential fast food customers. For the most part, I didnâ€™t record any of it. But you can find a few clips of our fast food hijinks if you scroll down on the PLA Sound Clips Archive page.

Finally we decided to capture a bit of our FCC violations on video. But instead of capturing actual customers being harassed by us as they placed an order, I drove through the Taco Bell drive-thru myself with a video camera sitting on the dashboard. As I attempted to place my order, RijilV informed me of some crazy new Taco Bell policies and a manager immediately rushed out to explain to me that I wasnâ€™t actually talking to an employee. Here is that video:

After spending several years on Google Video and YouTube, itâ€™s been watched approximately 20,000 times. And of those 20,000 people who have viewed it, approximately all of them have emailed me and asked me what kind of radio we used and how can they use a radio to do the same thing. So in the spirit of April 1st and in order to quell the number of emails sent to me and posts on the PLA Forums asking the same thing, Iâ€™ve decided to write this tutorial to help those people out.

But Iâ€™m not going to explain how to modify a Yaesu VX5 or a Yaesu VX7. A simple Google search will show you how to modify these ham radios. The problem with these mods is that, even though theyâ€™re fairly simple, you have to buy the radios which could cost you anywhere from $200 – $400. Then, after removing a couple solder points, you have to learn how to use it, you have to look up fast food frequency lists, you have to understand the difference between the transmit frequencies and the receive frequencies and you have to scroll through PL tones using trial and error to find the correct one.

Or how about we do this a different way. A way that uses a couple items that you might already have in your home. You can easily modify most old CB radios in a way that will allow them to transmit directly to drive-thru frequencies. You wonâ€™t have to scroll through hundreds of possible drive-thru frequencies, because a CB radioâ€™s channels line up in exactly the same way as most drive-thruâ€™s channels, only at a higher frequency. How do you get your CB radio to run at a higher frequency? A simple replacement of the crystal inside, with a 6.5536 MHz crystal. This triples the megahertz that are broadcast on and there is no learning required. You just take the modified CB radio to a fast food restaurant and start broadcasting to the customers.

â€œBut RBCP, I donâ€™t have a 6.5536 MHz crystal lying around my house,â€ you might be whining at this point. But this isnâ€™t true. Just about any house has several 6.5536 MHz crystals in them if you know where to look. This just happens to be the exact same crystal that you can find in electric heaters, hair dryers, electric stoves, curling irons, electric hot water heaters, irons, and toasters. These crystals are in just about any item that has heated coils and are used to control the frequency of the heating elements so that they donâ€™t burn your house down.

So for this modification you needâ€¦

1 CB radio. It has to be a 40 channel CB radio with a digital display, which includes just about any CB radio manufactured after the mid 1980â€™s. The old 23 channel CBs from the 1970â€™s will not work. It can even be a walkie talkie CB radio. If you donâ€™t have one, you can find one at Goodwill or a yard sale for probably less than $10.

1 toaster. (Or other item with heating elements inside.) A toaster is the most ideal to use, because itâ€™s almost guaranteed to have the crystal inside of it. Itâ€™s more common to find curling irons and hair dryers that donâ€™t. Again, it should be a toaster manufactured within the past 20 years or so. Before that they didnâ€™t have crystal requirements for toaster manufacturers. (And incidentally, there were a lot more electrical house fires back then.) Goodwill will probably have a toaster for less than $10.

1 soldering iron and solder. Donâ€™t worry if you donâ€™t have soldering experience. Itâ€™s actually pretty easy. Click here for a soldering tutorial. You can purchase a soldering iron at Radio Shack or Sears for about $10.

A few screwdrivers

Even if you have to buy all these materials, youâ€™re only out $30. Thatâ€™s a lot better than the $300 you might end up spending on a Yaesu radio. And some of you might already have all these items so you donâ€™t have to pay anything. Ask a friend or a relative if theyâ€™ve got an old toaster or CB radio lying around that they donâ€™t need.

First youâ€™ll want to take apart your toaster. This isnâ€™t too hard. Just flip it upside down and start removing the screws. Youâ€™ll probably need to pull off the plastic lever and knobs before you remove the top of the toaster. Once you have the top off, youâ€™ll see a green or brown circuit board inside.

Flip the circuit board down and youâ€™ll see all the components on the other side, including the 6.5536 MHz crystal. The crystal is silver and will have 6.5 stamped on the side of it. In the picture below, Iâ€™ve used an arrow to show you where itâ€™s located.

The crystal is likely in a different spot in other toasters, but itâ€™s hard to mistake for any other electronic component. The crystal will have some form of 6.5 stamped on the side of it. In my toaster, it showed 6.55-12. While the official frequency needed is 6.5536 MHz, anything within 1.6 megahertz will work. So donâ€™t worry if your crystal just says 6.5 or 6.50 – itâ€™s all the same for our purposes.

Itâ€™s kind of hard to see what Iâ€™m doing in the picture above, but Iâ€™m heating up the leads on the crystal from underneath with my soldering iron to melt the solder, and Iâ€™m pulling on the crystal from above with a pair of needle nose pliers. It only takes a few seconds to get the crystal out of the toaster.

Now that the crystal is out of your toaster, throw your toaster away! Do not attempt to use it once the crystal is removed. Remember, the crystal is in there for safety and using your toaster without the crystal could burn your toast and/or start a kitchen fire. Itâ€™s likely your toaster wonâ€™t even turn on with the missing crystal, but please donâ€™t even try. Just throw it away.

As I mentioned before, just about any brand and model of CB radio will work, as long as it has the digital display on it. Which means, just about any CB radio manufactured after the mid 1980â€™s. These are the kinds of CB radios whose frequencies are controlled by a single crystal inside of them. For my mod, I used a Radio Shack TRC-207 walkie talkie CB radio, which is pictured above. I prefer using a walkie talkie CB radio because it doesnâ€™t requiring sticking a huge CB antenna on the roof of my car which might be noticed if a fast food employee starts looking around the parking lot for the culprits.

Taking apart your CB radio is just as easy as taking apart the toaster. Remove the screws and pop it open. You may or may not have to lift up the circuit board inside to find the crystal inside. In my particular model, the crystal actually plugged into a socket so I didnâ€™t need to even desolder the old crystal. I just pulled it out with my fingers and then plugged in the new 6.55 MHz crystal. I donâ€™t know how common this is, because in other CB radios that Iâ€™ve modified the crystal was soldered to the circuit board, just like in the toaster.

Put your CB back together and test it to make sure itâ€™s working. Youâ€™re finished! Obviously, you wonâ€™t be able to talk on normal CB channels anymore since your CB is transmitting and receiving at a much higher frequency now. But who cares, CB channels are lame anyway. Letâ€™s hop in the car and drive to our nearest fast food establishment to test it out.

Sit near the drive-thru and wait for a customer to pull up. While the customer is talking to the drive-thru speaker, start flipping through your channels until you hear them talking. Iâ€™ve found that most drive thrus end up being somewhere in the 16 – 25 channel range. Iâ€™ve never found one above channel 30 and only a few on channels 1 through 15. It all depends on how their drive-thru is set up and what frequencies theyâ€™re using. Anyway, push down your talk button and start talking to the customer.

The cool thing about using a CB radio to transmit on drive-thru frequencies is that a CB is designed to work for several miles. The headsets that those fast food people wear are only designed to work for about 100 feet. So you can easily overpower the employees, even if youâ€™re several parking lots away. In fact, you may be inadvertently screwing with several other drive-thrus in town without even knowing it. This is more likely when youâ€™re using the kind of CB radio thatâ€™s supposed to be installed in a car. Those usually run on 5 watts and can cover an entire city. This is another reason I like to use my walkie talkie. Itâ€™s lucky if it will work for even a mile, so Iâ€™m only harassing one restaurant at a time.

If you found this tutorial useful, you might also enjoy the video Iâ€™ve made on the same subject. It includes much of the same information in this tutorial, but also includes actual footage of us messing with a drive-thru with this CB mod. Enjoy!

You might also enjoy our original Taco Bell Takeover video, our Happy Birthday drive-thru video and our Drive-Thru Shenanigans video.

PLA TV: Hijacking Fast Food Frequencies [9:12m]: Download (4913)

Local Copy

Amateur Radio and Radhaz

Posted by :Derek On : November 4, 2008

Something I have been very wary about for some year had begun to be better understood over the last few years.

I remember a doctor from an Adelaide hospital who presented at an IEEE meeting saying “on the record there hasn’t been enough research performed to prove that electromagnetic radiation causes cancer, but off the record I have seen enough cases where I am convinces it does”.

This simple statement and other examples provided during the presentation really drove home that we must be wary and respectful when using an existing near electromagnetic emitting devices.

This article came from the local South Australia Amature Radio Experimentes Group Website – Thanks for allthe great work. See link http://www.areg.org.au/info/radhaz/radhaz.html

General Background Information

The question of Radhaz has to be considered when you are constructing an Amateur Radio station that will operate near members of the general public as well as your self.

The responsibility for ensuring that the operation of an Amateur Radio transmitting station is operating with in the ARPANSA and ACMA guidelines is souly the responsibility of the amateur radio operator in control of the radio transmitter.

As the standard for Radiation Protection Standard for Maximum Exposure Levels to Radiofrequency Fields – 3 kHz to 300 GHz changes from time to time. The information on this web site will become out of date. AREG accepts no responsibility for the information presented on this page, the relative orginsations should be consolted for the latest up to date information.

For complete appraisal of your situation, you should consult one of the many orginsations that are NATA certified.

As of March 1st 2003, the Australian Communications & Media Authority (ACMA) introduced new limits for human exposure to electromagnetic radiation (EMR) covering all mobile transmitters such as remote controlled toys, walkie-talkies and hand held two-way radios as well as radio communications installations such as broadcast towers and amateur radio stations.

Under the new regulations, mandatory limits are set by the Australian Radiation Protection and Nuclear Safety Agency (ARPANSA) and people who hold a licence for a radiocommunications facility will have to comply, and in certain cases, hold records demonstrating compliance with the limits.

For a complete details on the ARPANSA standard, please refer to the link below and the ARPANSA web site.

http://www.arpansa.gov.au

maximum-exposure-levels-to-radiofrequency-fields

The RPS No:3 Standard is known as, Radiation Protection Standard for Maximum Exposure Levels to Radiofrequency Fields â€” 3 kHz to 300 GHz (2002).

This Standard specifies limits of human exposure to radiofrequency (RF) fields in the frequency range 3 kHz to 300 GHz, to prevent adverse health effects. These limits are defined in terms of basic restrictions for exposure of all or a part of the human body. Relevant derived reference levels are also provided as a practical means of showing compliance with the basic restrictions. In particular, this Standard specifies the following:

(a) Basic restrictions for occupational exposure with corresponding derived reference levels as a function of frequency.

(b) Basic restrictions for general public exposure, with corresponding derived reference levels as a function of frequency.

(c) Equipment and usage parameters in order to assist in the determination of compliance with this Standard.
The limits specified in this Standard are intended to be used as a basis for planning work procedures, designing protective facilities, the assessment of the efficacy of protective measures and practices, and guidance on health surveillance

IDEAS page is all about putting up design and other general ideas. These may include part circuits or drawings of things that we have thought other people may be interested in. In general don’t expect a complete package, as this page is only meant to give you some ideas on what we have done. So you can further your own experimentation.

Cisco Command Cheat Sheet

Posted by :Derek On : July 4, 2008

Category: Infrastructure, Internet

Tags:access, authentication, authentification, boot system, broadcast, cisco commands, data, DES, DNS, domain name services, EFT, encapsulation, Ethernet, frequency, hack, Infrastructure, interface, ISP, name server, network, password, phone, pvc, Relay, SAP, script, security, server, Shiraz, telnet, text, trunk, type

I found a list of useful Cisco commands which I though I would post here.

ROUTER COMMANDS `:`

Config# terminal editing – allows for enhanced editing commands
Config# terminal monitor – shows output on telnet session
Config# terminal ip netmask-format hexadecimal|bit-count|decimal – changes the format of subnet masks

HOST NAME:

Config# hostname ROUTER_NAME

BANNER:

Config# banner motd # TYPE MESSAGE HERE # – # can be substituted for any character, must start and finish the message

DESCRIPTIONS:

Config# description THIS IS THE SOUTH ROUTER – can be entered at the Config-if level

CLOCK:

Config# clock timezone Central -6
# clock set hh:mm:ss dd month yyyy – Example: clock set 14:13:00 25 August 2003

CHANGING THE REGISTER:

Config# config-register 0x2100 – ROM Monitor Mode
Config# config-register 0x2101 – ROM boot
Config# config-register 0x2102 – Boot from NVRAM

BOOT SYSTEM:

Config# boot system tftp FILENAME SERVER_IP – Example: boot system tftp 2600_ios.bin 192.168.14.2
Config# boot system ROM
Config# boot system flash – Then – Config# reload

CDP:

Config# cdp run – Turns CDP on
Config# cdp holdtime 180 – Sets the time that a device remains. Default is 180
Config# cdp timer 30 – Sets the update timer.The default is 60
Config# int Ethernet 0
Config-if# cdp enable – Enables cdp on the interface
Config-if# no cdp enable – Disables CDP on the interface
Config# no cdp run – Turns CDP off

HOST TABLE:

Config# ip host ROUTER_NAME INT_Address – Example: ip host lab-a 192.168.5.1
-or-
Config# ip host RTR_NAME INT_ADD1 INT_ADD2 INT_ADD3 – Example: ip host lab-a 192.168.5.1 203.23.4.2 199.2.3.2 – (for e0, s0, s1)

DOMAIN NAME SERVICES:

Config# ip domain-lookup – Tell router to lookup domain names
Config# ip name-server 122.22.2.2 – Location of DNS server
Config# ip domain-name cisco.com – Domain to append to end of names

CLEARING COUNTERS:

# clear interface Ethernet 0 – Clears counters on the specified interface
# clear counters – Clears all interface counters
# clear cdp counters – Clears CDP counters

STATIC ROUTES:

Config# ip route Net_Add SN_Mask Next_Hop_Add – Example: ip route 192.168.15.0 255.255.255.0 205.5.5.2
Config# ip route 0.0.0.0 0.0.0.0 Next_Hop_Add – Default route
-or-
Config# ip default-network Net_Add – Gateway LAN network

IP ROUTING:

Config# ip routing – Enabled by default
Config# router rip
-or-
Config# router igrp 100
Config# interface Ethernet 0
Config-if# ip address 122.2.3.2 255.255.255.0
Config-if# no shutdown

IPX ROUTING:

Config# ipx routing
Config# interface Ethernet 0
Config# ipx maximum-paths 2 – Maximum equal metric paths used
Config-if# ipx network 222 encapsulation sap – Also Novell-Ether, SNAP, ARPA on Ethernet. Encapsulation HDLC on serial
Config-if# no shutdown

ACCESS LISTS:

IP Standard	1-99
IP Extended	100-199
IPX Standard	800-899
IPX Extended	900-999
IPX SAP Filters	1000-1099

IP STANDARD:

Config# access-list 10 permit 133.2.2.0 0.0.0.255 – allow all src ip’s on network 133.2.2.0
-or-
Config# access-list 10 permit host 133.2.2.2 – specifies a specific host
-or-
Config# access-list 10 permit any – allows any address
Config# int Ethernet 0
Config-if# ip access-group 10 in – also available: out

IP EXTENDED:

Config# access-list 101 permit tcp 133.12.0.0 0.0.255.255 122.3.2.0 0.0.0.255 eq telnet
-protocols: tcp, udp, icmp, ip (no sockets then), among others
-source then destination address
-eq, gt, lt for comparison
-sockets can be numeric or name (23 or telnet, 21 or ftp, etc)
-or-
Config# access-list 101 deny tcp any host 133.2.23.3 eq www

-or-

Config# access-list 101 permit ip any any
Config# interface Ethernet 0
Config-if# ip access-group 101 outIPX STANDARD:
Config# access-list 801 permit 233 AA3 – source network/host then destination network/host

-or-

Config# access-list 801 permit -1 -1 – “-1” is the same as “any” with network/host addresses
Config# interface Ethernet 0
Config-if# ipx access-group 801 outIPX EXTENDED:
Config# access-list 901 permit sap 4AA all 4BB all
– Permit protocol src_add socket dest_add socket
-“all” includes all sockets, or can use socket numbers

-or-

Config# access-list 901 permit any any all any all
-Permits any protocol with any address on any socket to go anywhere
Config# interface Ethernet 0
Config-if# ipx access-group 901 inIPX SAP FILTER:
Config# access-list 1000 permit 4aa 3 – “3” is the service type

-or-

Config# access-list 1000 permit 4aa 0 – service type of “0” matches all services
Config# interface Ethernet 0
Config-if# ipx input-sap-filter 1000 – filter applied to incoming packets

-or-

Config-if# ipx output-sap-filter 1000 – filter applied to outgoing packets

NAMED ACCESS LISTS:

Config# ip access-list standard LISTNAME
-can be ip or ipx, standard or extended
-followed by the permit or deny list
Config# permit any
Config-if# ip access-group LISTNAME in
-use the list name instead of a list number
-allows for a larger amount of access-lists

PPP SETUP:

Config-if# encapsulation ppp
Config-if# ppp authentication chap pap
-order in which they will be used
-only attempted with the authentification listed
-if one fails, then connection is terminated
Config-if# exit
Config# username Lab-b password 123456
-username is the router that will be connecting to this one
-only specified routers can connect

-or-

Config-if# ppp chap hostname ROUTER
Config-if# ppp chap password 123456
-if this is set on all routers, then any of them can connect to any other
-set same on all for easy configuration

ISDN SETUP:

Config# isdn switch-type basic-5ess – determined by telecom
Config# interface serial 0
Config-if# isdn spid1 2705554564 – isdn “phonenumber” of line 1
Config-if# isdn spid2 2705554565 – isdn “phonenumber” of line 2
Config-if# encapsulation PPP – or HDLC, LAPD

DDR – 4 Steps to setting up ISDN with DDR Configure switch type

1. Config# isdn switch-type basic-5ess – can be done at interface config

2. Configure static routes
Config# ip route 123.4.35.0 255.255.255.0 192.3.5.5 – sends traffic destined for 123.4.35.0 to 192.3.5.5
Config# ip route 192.3.5.5 255.255.255.255 bri0 – specifies how to get to network 192.3.5.5 (through bri0)

3. Configure Interface
Config-if# ip address 192.3.5.5 255.255.255.0
Config-if# no shutdown
Config-if# encapsulation ppp
Config-if# dialer-group 1 – applies dialer-list to this interface
Config-if# dialer map ip 192.3.5.6 name Lab-b 5551212
connect to lab-b at 5551212 with ip 192.3.5.6 if there is interesting traffic
can also use “dialer string 5551212” instead if there is only one router to connect to

4. Specify interesting traffic
Config# dialer-list 1 ip permit any
-or-
Config# dialer-list 1 ip list 101 – use the access-list 101 as the dialer list

5. Other Options
Config-if# hold-queue 75 – queue 75 packets before dialing
Config-if# dialer load-threshold 125 either
-load needed before second line is brought up
-“125” is any number 1-255, where % load is x/255 (ie 125/255 is about 50%)
-can check by in, out, or either

Config-if# dialer idle-timeout 180
-determines how long to stay idle before terminating the session
-default is 120

FRAME RELAY SETUP:

Config# interface serial 0
Config-if# encapsulation frame-relay – cisco by default, can change to ietf
Config-if# frame-relay lmi-type cisco – cisco by default, also ansi, q933a
Config-if# bandwidth 56
Config-if# interface serial 0.100 point-to-point – subinterface
Config-if# ip address 122.1.1.1 255.255.255.0
Config-if# frame-relay interface-dlci 100
-maps the dlci to the interface
-can add BROADCAST and/or IETF at the end
Config-if# interface serial 1.100 multipoint
Config-if# no inverse-arp – turns IARP off; good to do
Config-if# frame-relay map ip 122.1.1.2 48 ietf broadcast
-maps an IP to a dlci (48 in this case)
-required if IARP is turned off
-ietf and broadcast are optional
Config-if# frame-relay map ip 122.1.1.3 54 broadcast

SHOW COMMANDS

Show access-lists – all access lists on the router
Show cdp – cdp timer and holdtime frequency
Show cdp entry * – same as next
Show cdp neighbors detail – details of neighbor with ip add and ios version
Show cdp neighbors – id, local interface, holdtime, capability, platform portid
Show cdp interface – int’s running cdp and their encapsulation
Show cdp traffic – cdp packets sent and received
Show controllers serial 0 – DTE or DCE status
Show dialer – number of times dialer string has been reached, other stats
Show flash – files in flash
Show frame-relay lmi – lmi stats
Show frame-relay map – static and dynamic maps for PVC’s
Show frame-relay pvc – pvc’s and dlci’s
Show history – commands entered
Show hosts – contents of host table
Show int f0/26 – stats of f0/26
Show interface Ethernet 0 – show stats of Ethernet 0
Show ip – ip config of switch
Show ip access-lists – ip access-lists on switch
Show ip interface – ip config of interface
Show ip protocols – routing protocols and timers
Show ip route – Displays IP routing table
Show ipx access-lists – same, only ipx
Show ipx interfaces – RIP and SAP info being sent and received, IPX addresses
Show ipx route – ipx routes in the table
Show ipx servers – SAP table
Show ipx traffic – RIP and SAP info
Show isdn active – number with active status
Show isdn status – shows if SPIDs are valid, if connected
Show mac-address-table – contents of the dynamic table
Show protocols – routed protocols and net_addresses of interfaces
Show running-config – dram config file
Show sessions – connections via telnet to remote device
Show startup-config – nvram config file
Show terminal – shows history size
Show trunk a/b – trunk stat of port 26/27
Show version – ios info, uptime, address of switch
Show vlan – all configured vlan’s
Show vlan-membership – vlan assignments
Show vtp – vtp configs

CATALYST COMMANDS
For Native IOS – Not CatOS

SWITCH ADDRESS:

Config# ip address 192.168.10.2 255.255.255.0
Config# ip default-gateway 192.168.10.1DUPLEX MODE:
Config# interface Ethernet 0/5 – “fastethernet” for 100 Mbps ports
Config-if# duplex full – also, half | auto | full-flow-control

SWITCHING MODE:

Config# switching-mode store-and-forward – also, fragment-free

MAC ADDRESS CONFIGS:

Config# mac-address-table permanent aaab.000f.ffef e0/2 – only this mac will work on this port
Config# mac-address-table restricted static aaab.000f.ffef e0/2 e0/3
-port 3 can only send data out port 2 with that mac
-very restrictive security
Config-if# port secure max-mac-count 5 – allows only 5 mac addresses mapped to this port

VLANS:

Config# vlan 10 name FINANCE
Config# interface Ethernet 0/3
Config-if# vlan-membership static 10TRUNK LINKS:
Config-if# trunk on – also, off | auto | desirable | nonegotiate
Config-if# no trunk-vlan 2
-removes vlan 2 from the trunk port
-by default, all vlans are set on a trunk port

CONFIGURING VTP:
Config# delete vtp – should be done prior to adding to a network
Config# vtp server – the default is server, also client and transparent
Config# vtp domain Camp – name doesn’t matter, just so all switches use the same
Config# vtp password 1234 – limited security
Config# vtp pruning enable – limits vtp broadcasts to only switches affected
Config# vtp pruning disableFLASH UPGRADE:
Config# copy tftp://192.168.5.5/configname.ios opcode – “opcode” for ios upgrade, “nvram” for startup config

DELETE STARTUP CONFIG:

Config# delete nvram

BGP:

show ip bgp – Displays entries in the BGP routing table.
show ip bgp injected-paths – Displays paths in the BGP routing table that were conditionally injected.
show ip bgp neighbors – Displays information about the TCP and BGP connections to neighbors.

BGP Conditional Route Injection:

Step 1 Router(config)# router bgp as-number
-Â Places the router in router configuration mode, and configures the router to run a BGP process.

Step 2 Router(config-router)# bgp inject-map ORIGINATE exist-map LEARNED_PATH
-Â Configures the inject-map named ORIGINATE and the exist-map named LEARNED_PATH for conditional route injection.

Step 3 Router(config-router)# exit
-Exits router configuration mode, and enters global configuration mode.

Step 4 Router(config)# route-map LEARNED_PATH permit sequence-number
– Configures the route map named LEARNED_PATH.

Step 5 Router(config-route-map)# match ip address prefix-list ROUTE
– Specifies the aggregate route to which a more specific route will be injected.

Step 6 Router(config-route-map# match ip route-source prefix-list ROUTE_SOURCE
– Configures the prefix list named ROUTE_SOURCE to redistribute the source of the route.
Note The route source is the neighbor address that is configured with the neighbor remote-as command. The tracked prefix must come from this neighbor in order for conditional route injection to occur.

Step 7 Router(config-route-map)# exit
– Exits route-map configuration mode, and enters global configuration mode.

Step 8 Router(config)# route-map ORIGINATE permit 10
– Configures the route map named ORIGINATE.

Step 9 Router(config-route-map)# set ip address prefix-list ORIGINATED_ROUTES
– Specifies the routes to be injected.

Step 10 Router(config-route-map)# set community community-attribute additive
– Configures the community attribute of the injected routes.

Step 11 Router(config-route-map)# exit
– Exits route-map configuration mode, and enters global configuration mode.

Step 12 Router(config)# ip prefix-list ROUTE permit 10.1.1.0/24
– Configures the prefix list named ROUTE to permit routes from network 10.1.1.0/24.

Step 13 Router(config)# ip prefix-list ORIGINATED_ROUTES permit 10.1.1.0/25
– Configures the prefix list named ORIGINATED_ROUTES to permit routes from network 10.1.1.0/25.

Step 14 Router(config)# ip prefix-list ORIGINATED_ROUTES permit 10.1.1.128/25
– Configures the prefix list named ORIGINATED_ROUTES to permit routes from network 10.1.1.0/25.

Step 15 Router(config)# ip prefix-list ROUTE_SOURCE permit 10.2.1.1/32
– Configures the prefix list named ROUTE_SOURCE to permit routes from network 10.2.1.1/32.
Note The route source prefix list must be configured with a /32 mask in order for conditional route injection to occur.

DHCP

Step 1 (config)# interface ethernet0/0
(config-if)#ip address 1.1.1.1 255.0.0.0
(config-if)# no shutdown
– Configure an IP address on the router’s Ethernet port, and bring up the interface. (On an existing router, you would have already done this.)

Step 2 (config)# ip dhcp pool mypool
– Create a DHCP IP address pool for the IP addresses you want to use.

Step 3 (dhcp-config)# network 1.1.1.0 /8
– Specify the network and subnet for the addresses you want to use from the pool.

Step 4 (dhcp-config)#domain-name mydomain.com
– Specify the DNS domain name for the clients.

Step 5 (dhcp-config)#dns-server 1.1.1.10 1.1.1.11
– Specify the primary and secondary DNS servers.

Step 6 (dhcp-config)#default-router 1.1.1.1
– Specify the default router (i.e., default gateway).

Step 7 (dhcp-config)#lease 7
– Specify the lease duration for the addresses you’re using from the pool.

Step 8 (dhcp-config)#exit
– Exit Pool Configuration Mode.

This takes you back to the global configuration prompt.

Next, exclude any addresses in the pool range that you don’t want to hand out.

For example, let’s say that you’ve decided that all IP addresses up to .100 will be for static IP devices such as servers and printers. All IP addresses above .100 will be available in the pool for DHCP clients.

Here’s an example of how to exclude IP addresses .100 and below:

Optional (config)#ip dhcp excluded-address 1.1.1.0 1.1.1.100

The full DHCP reference can be found on the CISCO site.

Common Commands and Troubleshooting

Set a password on the console line:
- configure terminal
- line console 0
- password â€˜ciscoâ€™
- login
Passwords are case sensitive.
You must configure a password on the VTY lines, without one no one will be able to telnet to the switch/router.
The default mode when logging into a switch/router via telnet or SSH is user exec mode, which is indicated by the â€˜>â€™ prompt.
To configure the switch/router you need to use the privileged EXEC mode. To do this you enter the enable command in user EXEC mode. The prompt is indicated with â€˜#â€™.
If both enable secret and enable password are set, the enable secret will be used.
The enable secret is encrypted (by default) where as the enable password is in clear text.
In a config containing an enable secret 5 â€˜hashâ€™ the 5 refers to the level of encryption being used.
If no enable password/secret has been set when someone telnets to the device, they will get a â€˜%No password setâ€™ message. Someone with physical access must set the password.
To place all telnet users directly into enable mode:
- configure terminal
- line vty 0 4
- privilege level 15
To put a specific user directly into privileged EXEC mode (enable mode)
- username superman privilege 15 password louise
Telnet sends all data including passwords in clear text which can be intercepted.
SSH encrypts all data preventing an attacker from intercepting it.
Setting up a local user/password login database for use with telnet:
- configure terminal
- line vty 0 4
- login local
- exit
- username telnetuser1 password secretpass
To set up SSH you need to create the local user database, the domain name must be specified with the ip domain-name command and a crypto key must be created with the crypto key generate rsa command. To enable SSH on the VTY lines, use the command transport input ssh.
If you connect two Cisco switches together and the lights donâ€™t go amber then green, but instead stays off. A straight through cable has been used instead of a crossover cable.
The term â€˜a switches management interfaceâ€™ normally refers to VLAN1.
Assign a default gateway using the ip default-gateway ipaddress command.
You can use the command interface range fasterthernet 0/1 â€“ 12 to select a range of interfaces to configure at once.
MOTD banner appears before login prompt.
The login banner appears before the login prompt but after the MOTD banner.
The banner exec appears after a successful logon.
line con 0 â€“ configuring the logging synchronous on the console port stops the router from displaying messages (like an interface state change) until it detects no input from the keyboard and not other output from the router, such as a show commands output.
exec-timeout x y (x=minutes, y=seconds) â€“ the default is 5 minutes. Can be disabled by setting x=0 y=0
Shortcut commands
- Up Arrow â€“ will show you the last command you entered. Control+P does the same thing.
- Down Arrow â€“ will bring you one command up in the command history. Control+N does the same thing.
- CTRL+A takes the cursor to the start of the current command.
- CTRL+E takes the cursor to the end of the current command.
- Left arrow or CTRL+B moves backwards (towards the start) of the command one character at a time.
- Right arrow or CTRL+P moves forwards (towards the end) of the command one character at a time.
- CTRL+D deletes one character (the same as backspace).
- ESC+B moves back one word in the current command.
- ESC+F moves forward one word in the current command.
show history command will show the last 10 commands run by default.
the history size can be increased individually on the console port and on the VTY lines with the history size x command.
Config modes
- config t R1<config> is the global configuration mode.
- line vty 0 4 R1<config-line> is the line config mode.
- interface fastethernet 0/1 R1<config-if> interface config mode.

Troubleshooting

Cisco Discovery Protocol (CDP) runs by default on Cisco routers and switches. It runs globally and on a per-interface level.
CDP discovers basic information about neighboring switches and routers.
On media that supports multicasts at the data link layer, CDP uses multicast frames. on other media, CDP sends a copy of the CDP update to any known data-link addresses.
The show cdp command shows CDP settings.
CDP can be disabled globally using the command no cdp run and re-enable using cdp run.
CDP can be disabled at an interface level using the no cdp enable command at the sub-interface level.
The command show cdp neighbor – lists one summary line of information about each neighbor. Including:
- Device ID â€“ the remote devices hostname.
- Local Interface â€“ the local switch/router interface connected to the remote host.
- Holdtime â€“ is the number of seconds the local device will retain the contents of the last CDP advertisement received from the remote host.
- Capability â€“ shows you the type of device the remote host is.
- Platform â€“ is the remote devices hardware platform.
- Port ID â€“ is the remote interface on the direct connection.
The command show cdp neighbor detail â€“ lists one large set (approx 15 lines) of information, one set for every neighbor. Including:
- The IOS version.
- VTP management domain.
- Management addresses.
show cdp entry name – lists the same information as the show cdp neighbors detail command, but only for the named neighbor (case sensitive).
show cdp â€“ states whether CDP is enabled globally, and lists the default update and holdtime timers.
show cdp traffic â€“ lists global statistics for the number of CDP advertisements sent and received.
show cdp interface type number – states whether CDP is enabled on each interface or a single interface if the interface is listed, and states the update and holdtime timers on those interfaces.
CDP should be disabled on interfaces it is not needed to limit risk of an attacker learning details about each switch or router. Use the no cdp enable interface subcommand to disable CDP and the cdp enable interface subcommand to re-enable it.
The command show cdp interface shows the CDP settings for every interface.
Interface status messages:
- Interface status is down/down â€“ this indicates a physical problem, most likely a loose or unplugged cable.
- Line protocol is down, up/down â€“ this indicates a problem at the logical level, most likely an encapsulation mismatch or a missing clock rate.
- Administratively down â€“ this indicates the interface has been shutdown and needs to be manually opened with the sub interface command no shutdown.
The command show mac-address-table shows the mac address table. show mac-address-table dynamic sows the dynamically learned entries only.
Most problems on a switch are caused by human error â€“ misconfiguration.
The command show debugging shows all the currently running debugs.
undebug all â€“ will turn all debugging off.
The command show vlan brief shows a switches VLAN configuration.
If pinging 127.0.0.1 fails on a pc, there is a problem with the local PC, most likely a bad install of TCP/IP.
On a pc the command netstat -rn shows the pcâ€™s routing table.
Additional Telnet commands:
- show sessions shows information about each telnet session, the where command does the same thing.
- resume x, x being the session number is used to resume a telnet session.
- To suspend a session use the command CTRL+ALT+6.
- To disconnect an open session use the command disconnect x, x being the session number.
Ping result codes:
- !!!!! â€“ IP connectivity to the destination is ok.
- â€¦.. â€“ IP connectivity to the destination does not exist.
- U.U.U â€“ the local router has a route to the destination, but a downstream router does not.
debug ip packet â€“ can help troubleshooting the above ping results.
When using traceroute or extended ping the Escape Sequence is: CTRL+SHIFT+6.
Extended ping can only be run from enable mode.
If a routing table contains multiple routes to the same destination with multiple next hops and the prefixes are different, the most specific (longest) prefix route will be used. If all of the prefix lengths are the same the Administrative Distance will be used. [AD/Metric].
Administrative Distance is a measure of a routes believability, with a lower AD being more believable than a route with a higher AD. AD only comes into play if the prefix lengths are the same.
You can set the Administrative Distance on a static route with the command ip route 55.55.55.0 255.255.255.0 192.168.1.2 150, you would do this to set a backup route if a dynamic route fails/is not available in the routing table.

Cisco NX-OS/IOS BGP (Advanced) Comparison

These may also assist: Undocumented Cisco Commands

Bluetooth – Security

Posted by :Derek On : March 24, 2008

Category: Bluetooth, Security

Tags:access, antenna, attack, authentification, Backdoor, bar, best practices, bluejacker, Bluejacking, Bluetooth, broadcast, Card, Commerce, Communications, Corporate, data, DES, development, Digital, Dust, EFT, Electronic, encryption, Enterprise, Ericsson, frequency, hack, Hacking, identity, Internet, JAVA, javascript, Mall, mechanisms, mobile phones, network, online, payment, personal area networks, phone, php, Pin, privacy, Radiation, Radio, script, security, Serious, Shiraz, SLA, SMS, SNARF, something, Technical, technique, technology, threat, Threats, transmission, web

Redirected from Bluetooth

Source

1 Bluetooth
2 Wireless- History
3 Wireless- Technologies
4 Bluetooth- Technical Introduction
5 Bluetooth- Advantages
6 Bluetooth- Applications
7 Bluetooth- Security Issues
7.1 The SNARF attack
7.2 The BACKDOOR attack
7.3 The BLUEBUG attack
7.4 Bluejacking
7.5 Warnibbling
8 Future of Bluetooth
9 See also:
10 Reference List

Bluetooth

Bluetooth is a new technology that utilises radio frequency waves as a way to communicate wirelessly between digital devices. It sets up personal area networks that incorporate all of a persons digital devices into one system for both convergence and convenience.

Wireless- History

Many people put the invention of [wireless] radio down to Guglielmo Marconi, who in 1895 sent the first radio telegraph transmission across the English Channel. Only twelve years later radio began being used in the public sphere. [Mathias, p.2] Up until then however, many wireless pioneers conducted trials across lakes where the antenna used to transmit the signal was longer than the distance across the lake. [Brodsky, p. 3] After its introduction the main use of wireless radio was for military communications where its first use was for the Boer War. [Flichy, p. 103] The invention of broadcast radio ensured the feasibility of wireless technologies. [Morrow, p. 2] By the 1920s, radio had become a well-recognised mass medium. [Flichy, p. 111] From the 1980s until now, wireless communications have been through several stages, from 1G (analogue signal), 2G (digital signal) and 3G (always on, faster data rate). [Lightman and Rojas, p. 3] The history of Bluetooth is a much more recent one, with the first Bluetooth-enabled products coming into existence in 2000. Named after Harald Blatand the first, king of Denmark around twelve hundred years ago, who joined the Danish and Norwegian kingdoms, Bluetooth technology is founded on this same unifying principle of being able to unite the computer and telecommunication industr[ies]. [Ganguli, p. 5] In 1994 the Ericsson Company began looking into the idea of replacing cables connecting accessories to mobile phones and computers with wireless links, and this became the main inspiration behind Bluetooth. [Morrow, p. 10]

Wireless- Technologies

Bluetooth is not the only wireless technology currently being developed and utilised. Other wireless technologies, including 802.11b, otherwise known as Wi-Fi, Infrared Data Association (IrDA), Ultra- Wideband Radio (UWB), and Home RF are being applied to similar technologies that Bluetooth use with mixed results. 802.11 is the most well known technology, excluding Bluetooth, and uses the same radio frequency, meaning that they are not compatible as they cause interference with each other. 802.11 is being implemented into universities in the US, Japan and China, as well as food and beverage shops where they are being used to identify students and customers. Even airports have taken up the 802.11 technology, with airports all over America, and three of Americas most prominent airlines promoting the use of it. [Lightman and Rojas, p. 202-3] Infrared Data Association is extremely inferior to that of Bluetooth. Its limitations include only being able to communicate point-to-point, needing a line of sight, and it has a speed of fifty- six kilobytes per second, whereas Bluetooth is one megabyte per second. [Ganguli, p. 17] The Ultra- Wideband Radio is superior to that of Bluetooth in that it can transmit at greater lengths (up to 70 metres), with only half of the power that Bluetooth uses. [Ganguli, p.17] HomeRF is a technology that is not very well known. It is used for data and voice communication and targeted for the residential market segment and does not serve enterprise- class WLANs, public access systems or fixed wireless Internet access. [Ganguli, p.17-18]

Bluetooth- Technical Introduction

Bluetooth is a short- range radio device that replaces cables with low power radio waves to connect electronic devices, whether they are portable or fixed. The Bluetooth device also uses frequency hopping to ensure a secure, quality link, and it uses ad hoc networks, meaning that it connects peer-to-peer. It can be operated worldwide and without a network because it uses the unlicensed Industrial- Scientific Medical (ISM) band for transmission that varies with a change in location. [Ganguli, p. 25-6] The Bluetooth user has the choice of point-to-point or point-to-multipoint links whereby communication can be held between two devices, or up to eight. [Ganguli, p. 96] When devices are communicating with each other they are known as piconets, and each device is designated as a master unit or slave unit, usually depending on who initiates the connection. However, both devices have the potential to be either a master or a slave. [Swaminatha and Elden, p. 49]

Bluetooth- Advantages

There are many advantages to using Bluetooth wireless technologies including the use of a radio frequency, the inexpensive cost of the device, replacing tedious cable connections, the low power use and implemented security measures. The use of an unlicensed radio frequency ensures that users do not need to gain a license in order to use it. Unlike Infrared which needs to have a line of sight in order to work, Bluetooth radio waves are omnidirectional and do not need a clear path. The device itself is relatively cheap and easy to use, one can be bought for around ten American dollars, and this price is currently decreasing. Compare this to the expensive cost of implementing hundreds of cables and wires into an office and there is no competition. Of course, this is the main reason for the take -up in Bluetooth -enabled devices; it does away with cables. Another of Bluetooths advantages is its low power use, ensuring that battery operated devices such as mobile phones and personal digital assistants wont have their battery life drained with the use of it. This low power consumption also guarantees minimal interruption from other radio operated and wireless devices that operate at a higher power. Bluetooth has several enabled security measures that ensures a level of privacy and security, including frequency hopping, whereby the device changes radio frequency sixteen hundred times per second. Also within the security tools are encryption and authentification mechanisms that guarantee little interference by unauthorised hackers. [Ganguli, p. 330] One of the best advantages of Bluetooth devices, especially the hands free device that connects to a mobile phone, is that it removes radiation from the brain region. [Tsang, p.1]

Bluetooth- Applications

The applications that are in development or current use for the Bluetooth technology include such areas as automotive, medical, industrial equipment, output equipment, digital -still cameras, computers, and communications systems. [Lightman and Rojas, p. 201] Bluetooth is an ad hoc network user, and therefore it may be used for social networking, i.e. people can meet and share files or link their Bluetooth devices together to play games or other such activities. [Smyth, p. 70] Using Bluetooth, a mobile phone can become a three- way phone, where at home it connects to a landline for cheaper calls, on the move it acts as a mobile phone and when it comes in contact with another Bluetooth-enabled phone it acts as a walkie- talkie. This walkie- talkie option allows for free interaction and communication, as Bluetooth is not connected to any telecommunications network. [Gupta, p.1] Bluetooth also allows automatic synchronization of your desktop, mobile computer, notebook and your mobile phone for the user to have all of their data managed as one. [Gupta, p.1]

Bluetooth- Security Issues

Bluetooth has several threats which range in level of risk and how widespread the action is. These threats have the ability to provide criminals with sensitive information on both corporate and personal levels. The only way to avoid such threats is for manufacturers, distributors, and consumers to be provided with more information on how they are committed, current attack activity and how to combat them. This information can be used on a technical level for manufacturers, it can be used by distributors at retail levels to teach consumers the risks and it can be used directly by consumers to be aware of the threats. The outcome of such research will allow end users of Bluetooth products to have an upper hand in this wireless warfare. Bluetooth security is in early stages with regards to both the attackers, their techniques and consumers understanding of these attacks. Some research has been conducted into what the attackers are doing and how they do it. Adam Laurie of A.L Digital Ltd http://www.thebunker.net/release-bluestumbler.htm is leading the research race in Bluetooth security and is often linked to academic resources. Laurie’s research has uncovered the following capabilities of Bluetooth attacks:

Confidential data such as the entire phone book, calender and the phone’s IMEI.
Complete memory contents of some mobile phones can be accessed by a previously trusted (“paired”) device that has since been removed from the trusted list.
Access can be gained to the AT command set of the device, giving full access to the higher level commands and channels, such as data, voice and messaging.

Attacks on Bluetooth devices at this stage are relatively new to consumers, and therefore are not widely seen as a real threat. Attacks such as the Bluejack attack are probably more recognised by consumers due to its perceived humorous and novelty nature as well as the ease to Bluejack someone. Users who allow their phone to be Bluejacked open the door to more serious attacks, such as the Backdoor attack which have a low level of awareness amongst consumers as attackers can attach to the device with out the users knowledge. Corporations are starting to understand the risks Bluetooth devices pose, Michael Ciarochi (in Brewin 2004) stated that ‘Bluetooth radios were included in laptop PCs that were being configured by an IT Engineer. It raises the possibility of opening a wireless back door into data stored on the PCs. Such a security weakness would be extremely attractive to hackers. Although Bluetooth invites hackers to such attacks; Bluetooth Venders are playing down the risks, Brewin (2004) said that ‘Bluetooth advocates last week dismissed growing security fears about the short-range wireless technology, saying any flaws are limited to a few mobile-phone models. They also detailed steps that users can take to secure Bluetooth devices’. There are many methods of Bluetooth attacks, the Snarf, the Backdoor, Bluebug, Bluejack and Warnibbling attack are the only recognised attacks at this early stage. Below are explanations of such attacks.

The SNARF attack

It is possible for attackers to connect to the device without alerting the user, once in the system sensitive data can be retrieved, such as the phone book, business cards, images, messages and voice messages.

http://www.salzburgresearch.at/research/gfx/bluesnarf_cebit2004.pdf

Local Copy: BlueSnarf_CeBIT2004.pdf

The BACKDOOR attack

The backdoor attack is a higher concern for Bluetooth users; it allows attackers to establishing a trust relationship through the “pairing” mechanism, but ensuring that the user can not see the target’s register of paired devices. In doing this attackers have access to all the data on the device, as well as access to use the modem or internet; WAP and GPRS gateways may be accessed without the owner’s knowledge or consent.

The BLUEBUG attack

This attack gives access to the AT command set, in other words it allows the attacker to make premium priced phone calls, allows the use of SMS, or connection the internet. Attackers can not only use the device for such fraudulent exercises it also allows identity theft to impersonate the user.

Bluejacking

Dibble (2004) explained that ‘Just as SMS was spawned, there’s a new craze that’s spreading across parts of Europe. Reportedly, it’s more prominent in the UK, but popular elsewhere too’. Bluejacking allows attackers to send messages to strangers in public via Bluetooth. When the phones ‘pair’ the attacked can write a message to the user. Although it may seem harmless at first, there is a downside. Once connected the attacker may then have access to any data on the users Bluetooth device, which has obvious concerns. Powell (2004: 22) explained that ‘Users can refuse any incoming message or data, so Bluejackers change their username to a short barb or compliment to beat you to the punch. For example, you might receive something along the lines of “Incoming message from: Dude, you’ve been Bluejacked.” Or, “Incoming message from: ROI is overrated.” Bluejacking is regarded as a smaller threat to Bluetooth as users being attacked are aware they have been Bluejacked. This does not mean however that they are aware that sensitive information is being accessed and used in a malicious manner.

http://www.bluejackq.com/

Warnibbling

Warnibbling is a hacking technique using Redfang, or similar software that allows hackers to reveal corporate or personal sensitive information. Redfang allows hackers to find Bluetooth devices in the area, once found, the software takes you through the process of accessing any data that is stored on that device. Redfang also allows non-discoverable devices to be found. Whitehouse explains when testing Redfang ‘One of the first obstacles we had to overcome was the discovery of non-discoverable devices (it was surprising to see the number of devices that dont by default implement this security measure)’. http://www.atstake.com/research/reports/acrobat/atstake_war_nibbling.pdf

Future of Bluetooth

Further information, and somewhat speculation is required for consumers and Bluetooth stakeholders on the future of Bluetooth. Such information will provide a clearer understanding of why security of Bluetooth must be improved. Luo and Lee (2004) provide a short term prediction of where Bluetooth is heading, Europe and Asian countries already offer electronic newspapers, subway tickets, and car parking fees via wireless devices. Collins (2003) says that Bluetooth devices ‘appear to be more secure than 802.11 wireless LANs. However, this situation may not last, as the Bluetooth technology becomes more widespread and attracts greater interest from the hacking community’.

http://www.arraydev.com/commerce/jibc/0402-10.htm

Reference List

Brodsky, I. (1995) Wireless: The Revolution in Personal Telecommunications, Massachussetts, USA: Artech House Inc, ISBN 0890067171 (Erin Watson)
Collins, G. (2003) Bluetooth Security. Byte.com [Online], Available: Academic Search Elite, ISSN:0360-5280 [Accessed 6/9/04]. (Ben Henzell)
Dibble, T (2003) ‘Bluejack city: a new wireless craze is spreading through Europe’ [Online]. Available: http://www.sys-con.com/Wireless/article.cfm?id=710 [Accessed 4/8/04. (Ben Henzell)
Finn, E. (2004) Be carefull when you cut the cord. Popular Science [Online], vol. 264, issue. 5, p30. Available: Ebsco Host: Academic Search Elite, ISSN:0161-7370 [Accessed 6/9/04]. (Ben Henzell)
Flichy, P. (1995) Dynamics of Modern Communication, London: Sage Publications, ISBN 0803978502 (Erin Watson)
Ganguli, M. (2002) Getting Started with Bluetooth, Ohio: Premier Press, ISBN 1931841837 (Erin Watson)
Gupta, P. 1999. Bluetooth Technology: What are the Applications?. http://www.mobileinfo.com/Bluetooth/applic.htm (accessed August 23, 2004). (Erin Watson)
Laurie, B & L (2003) Serious flaws in Bluetooth security lead to disclosure of personal data [Online]. Available: http://www.thebunker.net/release-bluestumbler.htm [Accessed 4th Aug 2004]. (Ben Henzell)
Lightman, A. and Rojas, W. (2002) Brave New Unwired World, New York, USA: John Wiley and Sons, Inc., ISBN 0471441104 (Erin Watson)
Luo, X. Lee, C. (2004). Micropayments in Wireless M-Commerce: Issues, Security, and Trend[Online]. Available: http://www.arraydev.com/commerce/jibc/0402-10.htm [Accessed 4/8/2004] (Ben Henzell)
Morrow, R. (2002) Bluetooth Operation and Use, New York, USA: The McGraw- Hill Companies, ISBN 007138779X (Erin Watson)
Powell, W. (2004) The Wild Wild Web T+D [Online], Vol. 58, issue. 1, p22. Available: Academic Search Elite, ISSN:1535-7740 [Accessed 6/9/04]. (Ben Henzell)
Smyth, P. (ed.)(2004) Mobile and Wireless Communications: Key Technologies and Future Applications, London, UK: The Institute of Electrical Engineers, ISBN 0863413684 (Erin Watson)
Swaminatha, T. and Elden, C. (2003) Wireless Security and Privacy: Best Practices and Design Techniques, Massachussetts, USA: Pearson Education, Inc., ISBN 0201760347 (Erin Watson)
Tsang, W. et al. Date unknown. Bluetooth Applications. http://ntrg.cs.tcd.ie/undergrad/4ba2.01/group3/applications.html (accessed August 23, 2004). (Erin Watson)
Whitehouse, O. (2003).’War Nibbling: Bluetooth Insecurity’ [Online]. Available: http://www.atstake.com/research/reports/acrobat/atstake_war_nibbling.pdf [Accessed 9/8/04] (Ben Henzell)

Erin Watson 08:47, 8 Sep 2004 (EST) â€“nhenzell 12:30, 8 Sep 2004 (EST)

Serious flaws in bluetooth security lead to disclosure of personal data

Posted by :madrock.net On : March 24, 2008

Category: Bluetooth, Security

Tags:access, ASP, attack, authenticate, authentication, Backdoor, bar, bluejacker, Bluejacking, Bluetooth, broadcast, Card, Communications, Corporate, Credit, data, DES, Digital, EFT, environment, Ericsson, hack, Hacking, handshake, identity, integration, interface, Internet, ISP, JAVA, javascript, Mall, mechanisms, mobile phones, network, online, patch, phone, Pin, Protection, RSA, script, security, Serious, Shiraz, Siemens, SLA, SMS, SNARF, something, Technical, technique, technology, text, Vulnerabilities, vulnerability, Vulnerable

source

Summary
In November 2003, Adam Laurie of A.L. Digital Ltd. discovered that there are serious flaws in the authentication and/or data transfer mechanisms on some bluetooth enabled devices. Specifically, three vulnerabilities have been found:

Firstly, confidential data can be obtained, anonymously, and without the owner’s knowledge or consent, from some bluetooth enabled mobile phones. This data includes, at least, the entire phone book and calendar, and the phone’s IMEI.

Secondly, it has been found that the complete memory contents of some mobile phones can be accessed by a previously trusted (“paired”) device that has since been removed from the trusted list. This data includes not only the phonebook and calendar, but media files such as pictures and text messages. In essence, the entire device can be “backed up” to an attacker’s own system.

Thirdly, access can be gained to the AT command set of the device, giving full access to the higher level commands and channels, such as data, voice and messaging. This third vulnerability was identified by Martin Herfurt, and they have since started working together on finding additional possible exploits resulting from this vulnerability.

Finally, the current trend for “Bluejacking” is promoting an environment which puts consumer devices at greater risk from the above attacks.
Vulnerabilities

The SNARF attack:
It is possible, on some makes of device, to connect to the device without alerting the owner of the target device of the request, and gain access to restricted portions of the stored data therein, including the entire phonebook (and any images or other data associated with the entries), calendar, real-time clock, business card, properties, change log, IMEI (International Mobile Equipment Identity [6], which uniquely identifies the phone to the mobile network, and is used in illegal phone ‘cloning’). This is normally only possible if the device is in “discoverable” or “visible” mode, but there are tools available on the Internet that allow even this safety net to be bypassed[4]. Further details will not be released at this time (see below for more on this), but the attack can and will be demonstrated to manufacturers and press if required.

The BACKDOOR attack:
The backdoor attack involves establishing a trust relationship through the “pairing” mechanism, but ensuring that it no longer appears in the target’s register of paired devices. In this way, unless the owner is actually observing their device at the precise moment a connection is established, they are unlikely to notice anything untoward, and the attacker may be free to continue to use any resource that a trusted relationship with that device grants access to (but note that so far we have only tested file transfers). This means that not only can data be retrieved from the phone, but other services, such as modems or Internet, WAP and GPRS gateways may be accessed without the owner’s knowledge or consent. Indications are that once the backdoor is installed, the above SNARF attack will function on devices that previously denied access, and without the restrictions of a plain SNARF attack, so we strongly suspect that the other services will prove to be available also.

The BLUEBUG attack:
The bluebug attack creates a serial profile connection to the device, thereby giving full access to the AT command set, which can then be exploited using standard off the shelf tools, such as PPP for networking and gnokii for messaging, contact management, diverts and initiating calls. With this facility, it is possible to use the phone to initiate calls to premium rate numbers, send sms messages, read sms messages, connect to data services such as the Internet, and even monitor conversations in the vicinity of the phone. This latter is done via a voice call over the GSM network, so the listening post can be anywhere in the world. Bluetooth access is only required for a few seconds in order to set up the call. Call forwarding diverts can be set up, allowing the owner’s incoming calls to be intercepted, either to provide a channel for calls to more expensive destinations, or for identity theft by impersonation of the victim.

Bluejacking:
Although known to the technical community and early adopters for some time, the process now known as “Bluejacking”[1] has recently come to the fore in the consumer arena, and is becoming a popular mechanism for exchanging anonymous messages in public places. The technique involves abusing the bluetooth “pairing”[2] protocol, the system by which bluetooth devices authenticate each other, to pass a message during the initial “handshake” phase. This is possible because the “name” of the initiating bluetooth device is displayed on the target device as part of the handshake exchange, and, as the protocal allows a large user defined name field – up to 248 characters – the field itself can be used to pass the message. This is all well and good, and, on the face of it, fairly harmless, but, unfortunately, there is a down side. There is a potential security problem with this, and the more the practice grows and is accepted by the user community, and leveraged as a marketing tool by the vendors, the worse it will get. The problem lies in the fact that the protocol being abused is designed for information exchange. The ability to interface with other devices and exchange, update and synchronise data, is the raison d’Ãªtre of bluetooth. The bluejacking technique is using the first part of a process that allows that exchange to take place, and is therefore open to further abuse if the handshake completes and the “bluejacker” successfully pairs with the target device. If such an event occurs, then all data on the target device becomes available to the initiator, including such things as phone books, calendars, pictures and text messages. As the current wave of PDA and telephony integration progresses, the volume and quality of such data will increase with the devices’ capabilities, leading to far more serious potential compromise. Given the furore that irrupted when a second-hand Blackberry PDA was sold without the previous owner’s data having been wiped[3], it is alarming to think of the consequences of a single bluejacker gathering an entire corporate staff’s contact details by simply attending a conference or camping outside their building or in their foyer with a bluetooth capable device and evil intent. Of course, corporates are not the only potential targets – a bluejacking expedition to, say, The House of Commons, or The US Senate, could provide some interesting, valuable and, who’s to say, potentially damaging or compromising data.<<<

The above may sound alarmist and far fetched, and the general reaction would probably be that most users would not be duped into allowing the connection to complete, so the risk is small. However, in today’s society of instant messaging, the average consumer is under a constant barrage of unsolicited messages in one form or another, whether it be by SPAM email, or “You have won!” style SMS text messages, and do not tend to treat them with much suspicion (although they may well be sceptical about the veracity of the offers). Another message popping up on their ‘phone saying something along the lines of “You have won 10,000 pounds! Enter this 4 digit PIN number and then dial 0900-SUCKER to collect your prize!” is unlikely to cause much alarm, and is more than likely to succeed in many cases.

Workarounds and fixes
We are not aware of any workarounds for the SNARF or BLUEBUG attacks at this time, other than to switch off bluetooth. For permanent fixes, see the ‘Fixes’ section at the bottom of the page.

To permanently remove a pairing, and protect against future BACKDOOR attacks, it seems you must perform a factory reset, but this will, of course, erase all your personal data.

To avoid Bluejacking, “just say no”.

The above methods work to the best of our knowledge, but, as the devices affected are running closed-source proprietary software, it not possible to verify that without the collaboration of the manufacturers. We therefore make no claims as to the level of protection they provide, and you must continue to use bluetooth at your own risk.

Who’s Vulnerable
To date the quantity of devices tested is not great. However, due to the fact that they are amongst the most popular brands, we still consider the affected group to be large. It is also assumed that there are shared implementations of the bluetooth stack, so what affects one model is likely to affect others. This table is accurate to the best of our knowledge, but without the cooperation of the manufacturers (which we currently do not have), it is not possible to conduct more extensive validation.

The devices known to be vulnerable at this time are:

Vulnerability Matrix ( = NOT Vulnerable)*
Make	Model	Firmware Rev	BACKDOOR	SNARF when Visible	SNARF when NOT Visible	BUG
Ericsson	T68	20R1B 20R2A013 20R2B013 20R2F004 20R5C001	?	Yes	No	No
Sony Ericsson	R520m	20R2G	?	Yes	No	?
Sony Ericsson	T68i	20R1B 20R2A013 20R2B013 20R2F004 20R5C001	?	Yes	?	?
Sony Ericsson	T610	20R1A081 20R1L013 20R3C002 20R4C003 20R4D001	?	Yes	No	?
Sony Ericsson	T610	20R1A081	?	?	?	Yes
Sony Ericsson	Z1010	?	?	Yes	?	?
Sony Ericsson	Z600	20R2C007 20R2F002 20R5B001	?	Yes	?	?
Nokia	6310	04.10 04.20 4.07 4.80 5.22 5.50	?	Yes	Yes	?
Nokia	6310i	4.06 4.07 4.80 5.10 5.22 5.50 5.51	No	Yes	Yes	Yes
Nokia	7650	?	Yes	No (+)	?	No
Nokia	8910	?	?	Yes	Yes	?
Nokia	8910i	?	?	Yes	Yes	?
* Siemens	S55	?	No	No	No	No
* Siemens	SX1	?	No	No	No	No
Motorola	V600 (++)	?	No	No	No	Yes
Motorola	V80 (++)	?	No	No	No	Yes

+ We now believe the 7650 is only vulnerable to SNARF if it has already been BACKDOORed.
++ The V600 and V80 are discoverable for only 60 seconds, when first powered on or when this feature is user selected, and the window for BDADDR discovery is therefore very small. Motorola have stated that they will correct the vulnerability in current firmware.

Disclosure
What is the Philosophy of Full Disclosure, and why are we providing the tools and detailing the methods that allow this to be done? The reasoning is simple – by exposing the problem we are achieving two goals: firstly, to alert users that the dangers exist, in order that they can take their own precautions against compromise, and secondly, to put pressure on manufacturers to rectify the situation. Consumers have a right to expect that their confidential data is treated as such, and is not subject to simple compromise by poorly implemented protocols on consumer devices. Manufacturers have a duty of care to ensure that such protection is provided, but, in practice, commercial considerations will often take precedence, and, given the choice, they may choose to simply supress or hide the problem, or, even worse, push for laws that prevent the discovery and/or disclosure of such flaws[5]. In our humble opinion, laws provide scant consumer protection against the lawless.

After 13 months, and in consideration of the fact that affected manufacturers had acknowledged the issues and made updated firmware available, Full Disclosure took place at the Chaos Computer Club’s annual congress – 21C3, in Berlin, 2004.

Slides from the disclosure talk can be found here: http://trifinite.org/Downloads/21c3_Bluetooth_Hacking.pdf

Tools
Proof of concept utilities have been developed, but are not yet available in the wild. They are:

bluestumbler – Monitor and log all visible bluetooth devices (name, MAC, signal strength, capabilities), and identify manufacturer from MAC address lookup.
bluebrowse – Display available services on a selected device (FAX, Voice, OBEX etc).
bluejack – Send anoymous message to a target device (and optionally broadcast to all visible devices).
bluesnarf – Copy data from target device (everything if pairing succeeds, or a subset in other cases, including phonebook and calendar. In the latter case, user will not be alerted by any bluejack message).
bluebug – Set up covert serial channel to device.
Tools will not be released at this time, so please do not ask. However, if you are a bona-fide manufacturer of bluetooth devices that we have been otherwise unable to contact, please feel free to get in touch for more details on how you can identify your device status.

Credits
The above vulnerabilities were discovered by Adam Laurie, during the course of his work with A.L. Digital, in November 2003, and this announcement was prepared thereafter by Adam and Ben Laurie for immediate release.

Adam Laurie is Managing Director and Chief Security Officer of A.L. Digital Ltd.

Ben Laurie is Technical Director of A.L. Digital, and author of Apache-SSL and contributor to many other open source projects, too numerous to expand on here.

A.L. Digital Ltd. are the owner operators of The Bunker, the world’s most secure data centre(s).
e: adam@algroup.co.uk
w: http://www.aldigital.co.uk

e: ben@algroup.co.uk
w: http://www.apache-ssl.org/ben.html

Further information relating to this disclosure will be updated at http://www.bluestumbler.org

References:
[1]

[2]

http://www.palowireless.com/infotooth/tutorial/lmp.asp

[3]

www.outlaw.com

[4]

bluesniff
btscanner
redfang

[5]

http://www.eff.org/

[6]

http://www.babt.com/gsm-imei-number-allocation.asp
http://www.mobiledia.com/glossary/68.html
- The Bluetooth SIG.
- Bruce Potter’s Defcon-11 presentation [Powerpoint].
- @Stake’s Bluetooth Discovery Paper [PDF].
- Marcel Holtmann’s German papers.
- Marcel Holtmann’s other papers.
- Bluetooth Device Security Database.
- Martin Herfurt’s CeBIT snarfing expedition.
- Slides from Blackhat/DEFCON talk.
- Nokia releases patches.

In the news

Bluetooth Wireless Specification

Posted by :madrock.net On : March 24, 2008

Category: Bluetooth, Radio General, Security

Tags:access, algorithm, antenna, architecture, ASP, attack, authenticate, authentication, Bluejacking, Bluetooth, bluetooth profiles, bluetooth special interest group, broadcast, Card, Chip, Communications, Cryptographically, data, DES, Digital, Dust, EDR, EFT, Electronic, encryption, environment, Ericsson, Ethernet, frequency, GHz, Guide, hardware, HCI, identification, identity, interface, ISP, JAVA, javascript, Mall, mobile phones, network, personal area networks, phone, php, Pin, Radio, RSA, SAP, scatternet, script, security, security concerns, Serious, Shiraz, SLA, SNARF, standards, support, Technical, technology, template, transmission, trunk, USB, VOIP, Vulnerable, web, wireless personal area, wireless personal area networks

Source

This article is about the Bluetooth wireless specification. For King Harold Bluetooth, see Harold I of Denmark

Bluetooth is an industrial specification for wireless personal area networks (PANs).

Bluetooth provides a way to connect and exchange information between devices like personal digital assistants (PDAs), mobile phones, laptops, PCs, printers and digital cameras via a secure, low-cost, globally available short range radio frequency.

Bluetooth lets these devices talk to each other when they come in range, even if they’re not in the same room, as long as they are within 10 metres (32 feet) of each other.

The spec was first developed by Ericsson, later formalised by the Bluetooth Special Interest Group (SIG). The SIG was formally announced on May 20, 1999. It was established by Sony Ericsson, IBM, Intel, Toshiba and Nokia, and later joined by many other companies as Associate or Adopter members.

* 1 About the name
* 2 General information
o 2.1 Embedded Bluetooth
* 3 Features by version
o 3.1 Bluetooth 1.0 and 1.0B
o 3.2 Bluetooth 1.1
o 3.3 Bluetooth 1.2
o 3.4 Bluetooth 2.0
* 4 Future Bluetooth uses
* 5 Security concerns
* 6 Bluetooth profiles
* 7 See also
* 8 External links

About the name

The system is named after a Danish king Harald BlÃ¥tand (<arold Bluetooth in English), King of Denmark and Norway from 935 and 936 respectively, to 940 known for his unification of previously warring tribes from Denmark, Norway and Sweden. Bluetooth likewise was intended to unify different technologies like computers and mobile phones. The Bluetooth logo merges the Nordic runes for H and B.

General information

A typical Bluetooth mobile phone headset

The latest version currently available to consumers is 2.0, but few manufacturers have started shipping any products yet. Apple Computer, Inc. offered the first products supporting version 2.0 to end customers in January 2005. The core chips have been available to OEMs (from November 2004), so there will be an influx of 2.0 devices in mid-2005. The previous version, on which all earlier commercial devices are based, is called 1.2.

Bluetooth is a wireless radio standard primarily designed for low power consumption, with a short range (up to 10 meters [1], ) and with a low-cost transceiver microchip in each device.

It can be used to wirelessly connect peripherals like printers or keyboards to computers, or to have PDAs communicate with other nearby PDAs or computers.

Cell phones with integrated Bluetooth technology have also been sold in large numbers, and are able to connect to computers, PDAs and, specifically, to handsfree devices. BMW was the first motor vehicle manufacturer to install handsfree Bluetooth technology in its cars, adding it as an option on its 3 Series, 5 Series and X5 vehicles. Since then, other manufacturers have followed suit, with many vehicles, including the 2004 Toyota Prius and the 2004 Lexus LS 430. The Bluetooth car kits allow users with Bluetooth-equipped cell phones to make use of some of the phone’s features, such as making calls, while the phone itself can be left in a suitcase or in the boot/trunk, for instance.

The standard also includes support for more powerful, longer-range devices suitable for constructing wireless LANs.

A Bluetooth device playing the role of “master” can communicate with up to 7 devices playing the role of “slave”. At any given instant in time, data can be transferred between the master and one slave; but the master switches rapidly from slave to slave in a round-robin fashion. (Simultaneous transmission from the master to multiple slaves is possible, but not used much in practice). These groups of up to 8 devices (1 master and 7 slaves) are called piconets.

The Bluetooth specification also allows connecting two or more piconets together to form a scatternet, with some devices acting as a bridge by simultaneously playing the master role in one piconet and the slave role in another piconet. These devices have yet to come, though are supposed to appear within the next two years.

Any device may perform an “inquiry” to find other devices to which to connect, and any device can be configured to respond to such inquiries.

Pairs of devices may establish a trusted relationship by learning (by user input) a shared secret known as a “passkey”. A device that wants to communicate only with a trusted device can cryptographically authenticate the identity of the other device. Trusted devices may also encrypt the data that they exchange over the air so that no one can listen in.

The protocol operates in the license-free ISM band at 2.45 GHz. In order to avoid interfering with other protocols which use the 2.45 GHz band, the Bluetooth protocol divides the band into 79 channels (each 1 MHz wide) and changes channels up to 1600 times per second. Implementations with versions 1.1 and 1.2 reach speeds of 723.1 kbit/s. Version 2.0 implementations feature Bluetooth Enhanced Data Rate (EDR), and thus reach 2.1 Mbit/s. Technically version 2.0 devices have a higher power consumption, but the three times faster rate reduces the transmission times, effectively reducing consumption to half that of 1.x devices (assuming equal traffic load).

Bluetooth differs from Wi-Fi in that the latter provides higher throughput and covers greater distances but requires more expensive hardware and higher power consumption. They use the same frequency range, but employ different multiplexing schemes. While Bluetooth is a cable replacement for a variety of applications, Wi-Fi is a cable replacement only for local area network access. A glib summary is that Bluetooth is wireless USB whereas Wi-Fi is wireless Ethernet.

Many USB Bluetooth adapters are available, some of which also include an IrDA adapter.

Embedded Bluetooth

Bluetooth devices and modules are increasingly being made available which come with an embedded stack and a standard UART port. The UART protocol can be as simple as the industry standard AT protocol, which allows the device to be configured to cable replacement mode. This means it now only takes a matter of hours (instead of weeks) to enable legacy wireless products that communicate via UART port.

Features by version

Bluetooth 1.0 and 1.0B

Versions 1.0 and 1.0B had numerous problems and the various manufacturers had great difficulties in making their products interoperable. 1.0 and 1.0B also had mandatory Bluetooth Hardware Device Address (BD_ADDR) transmission in the handshaking process, rendering anonymity impossible at a protocol level, which was a major set-back for services planned to be used in Bluetooth environments, such as Consumerism.

Bluetooth 1.1

In version 1.1 many errata found in the 1.0B specifications were fixed. There was added support for non-encrypted channels.

Bluetooth 1.2

This version is backwards compatible with 1.1 and the major enhancements include

Adaptive Frequency Hopping (AFH), which improves resistance to radio interference by avoiding using crowded frequencies in the hopping sequence
Higher transmission speeds in practice
extended Synchronous Connections (eSCO), which improves voice quality of audio links by allowing retransmissions of corrupted packets.
Received Signal Strength Indicator (RSSI)
Host Controller Interface (HCI) support for 3-wire UART
HCI access to timing information for Bluetooth applications.

Bluetooth 2.0

This version is backwards compatible with 1.x and the major enhancements include

Non-hopping narrowband channel(s) introduced. These are faster but have been criticised as defeating a built-in security mechanism of earlier versions; however frequency hopping is hardly a reliable security mechanism by today’s standards. Rather, Bluetooth security is based mostly on cryptography.
Broadcast/multicast support. Non-hopping channels are used for advertising Bluetooth service profiles offered by various devices to high volumes of Bluetooth devices simultaneously, since there is no need to perform handshaking with every device. (In previous versions the handshaking process takes a bit over one second.)
Enhanced Data Rate (EDR) of 2.1 Mbit/s.
Built-in quality of service.
Distributed media-access control protocols.
Faster response times.
Halved power consumption due to shorter duty cycles.

Future Bluetooth uses

One of the ways Bluetooth technology may become useful is in Voice over IP. When VOIP becomes more widespread, companies may find it unnecessary to employ telephones physically similar to today’s analogue telephone hardware. Bluetooth may then end up being used for communication between a cordless phone and a computer listening for VOIP and with an infrared PCI card acting as a base for the cordless phone. The cordless phone would then just require a cradle for charging. Bluetooth would naturally be used here to allow the cordless phone to remain operational for a reasonably long period.

Security concerns

In November 2003, Ben and Adam Laurie from A.L. Digital Ltd. discovered that serious flaws in Bluetooth security lead to disclosure of personal data (see http://bluestumbler.org). It should be noted however that the reported security problems concerned some poor implementations of Bluetooth, rather than the protocol itself.

In a subsequent experiment, Martin Herfurt from the trifinite.group was able to do a field-trial at the CeBIT fairgrounds showing the importance of the problem to the world. A new attack called BlueBug was used for this experiment.

In April 2004, security consultants @Stake revealed a security flaw that makes it possible to crack into conversations on Bluetooth based wireless headsets by reverse engineering the PIN.

This is one of a number of concerns that have been raised over the security of Bluetooth communications. In 2004 the first purported virus using Bluetooth to spread itself among mobile phones appeared for the Symbian OS. The virus was first described by Kaspersky Labs and requires users to confirm the installation of unknown software before it can propagate. The virus was written as a proof-of-concept by a group of virus writers known as 29a and sent to anti-virus groups. Because of this, it should not be regarded as a security failure of either Bluetooth or the Symbian OS. It has not propagated ‘in the wild’.

In August 2004, a world-record-setting experiment (see also Bluetooth sniping) showed that with directional antennas the range of class 2 Bluetooth radios could be extended to one mile. This enables attackers to access vulnerable Bluetooth-devices from a distance beyond expectation.

Bluetooth uses the SAFER+ algorithm for authentication and key generation.

Bluetooth profiles

In order to use Bluetooth, a device must be able to interpret certain Bluetooth profiles. These define the possible applications. Following profiles are defined:

Generic Access Profile (GAP)
Service Discovery Application Profile (SDAP)
Cordless Telephony Profile (CTP)
Intercom Profile (IP)
Serial Port Profile (SPP)
Headset Profile (HSP)
Dial-up Networking Profile (DUNP)
Fax Profile
LAN Access Profile (LAP)
Generic Object Exchange Profile (GOEP)
Object Push Profile (OPP)
File Transfer Profile (FTP)
Synchronisation Profile (SP)

This profile allows synchronisation of Personal Information Manager (PIM) items. As this profile originated as part of the infra-red specifications but has been adopted by the Bluetooth SIG to form part of the main Bluetooth specification, it is also commonly referred to as IrMC Synchronisation.

Hands-Free Profile (HFP)
Human Interface Device Profile (HID)
Hard Copy Replacement Profile (HCRP)
Basic Imaging Profile (BIP)
Personal Area Networking Profile (PAN)
Basic Printing Profile (BPP)
Advanced Audio Distribution Profile (A2DP)
Audio Video Remote Control Profile (AVRCP)
SIM Access Profile (SAP)

Compatibility of products with profiles can be verified on the Bluetooth Qualification website.

External links

Bluetooth Tutorial Includes information on Architecture, Protocols, Establishing Connections, Security and Comparisons
Bluetooth connecting and paire guide
The Official BluetoothÂ® Wireless Info Site<SIG public pages
Howstuffworks.com explanation of bluetooth
The Bluetooth Car Concept
A series of guides on how-to connect devices like mobile phones, PDAs, desktop/laptops, headsets and use different Bluetooth services
Mapping Salutation Architecture APIs to Bluetooth Service Discovery Layer
Bluetoothâ„¢ Security White Paper
Security Concerns
Laptops, PDA and mobile (cell) phones with Bluetooth(TM) and Linux
Bluetooth qualified products
Bluecarkit discussion forum about Bluetooth car handsfree
Bluetooth in spanish
Radio-Electronics.ComÂ â€“ Overview of Bluetooth and its operationi>
Bluetooth Background information about bluetooth (German)
Bluetooth.orgÂ â€“ The Official Bluetooth Membership Sitei>

Archives for : broadcast

Equipment suppliers and manufacturers

Electronic service

ROUTER COMMANDS :

These may also assist: Undocumented Cisco Commands

Bluetooth

Wireless- History

Wireless- Technologies

Bluetooth- Technical Introduction

Bluetooth- Advantages

Bluetooth- Applications

Bluetooth- Security Issues

The SNARF attack

The BACKDOOR attack

The BLUEBUG attack

Bluejacking

Warnibbling

Future of Bluetooth

See also:

Reference List

Table of contents

About the name

General information

Embedded Bluetooth

Features by version

Bluetooth 1.0 and 1.0B

Bluetooth 1.1

Bluetooth 1.2

Bluetooth 2.0

Future Bluetooth uses

Security concerns

Bluetooth profiles

See also

External links

Categories

Archives

Blogrolls

ROUTER COMMANDS `:`