16.05.2014 Views

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

Wireless Security.pdf - PDF Archive

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

464 Chapter 19<br />

Device A: Master<br />

Device B: Slave<br />

BD_ADDR (A)<br />

RAND A<br />

BD_ADDR (A)<br />

clock (A)<br />

E0<br />

clock (A)<br />

E0<br />

Kc<br />

Kc<br />

Kstr<br />

Kstr<br />

Data A→B<br />

Data A→B<br />

Data<br />

Data B→A<br />

Data B→A<br />

Figure 19.9: Bluetooth encryption<br />

Preamble<br />

Access code Header Data<br />

Sync word<br />

Trailer<br />

LT_<br />

ADDR<br />

Type<br />

Flow,<br />

ARQN,<br />

SEQN<br />

HEC<br />

Payload<br />

Figure 19.10: Bluetooth packet format<br />

the ciphertext. There are a few important things to note about the encryption process in<br />

Bluetooth.<br />

First, not all bits of the Bluetooth packet are encrypted. Figure 19.10 shows the format<br />

of a Bluetooth packet. It consists of an access code followed by a header and finally the<br />

payload. The access code is derived from the BD_ADDR of the master of the piconet and<br />

since every piconet has a unique master, the access code uniquely identifies a piconet.<br />

The access code is therefore used by the devices in a piconet to determine if a packet is<br />

for another piconet, in which case the packet is discarded.<br />

The access code also defines where a slot boundary lies and is therefore also used by the<br />

slaves in a piconet to synchronize their clocks to the master’s clock. It is therefore not<br />

a surprise that the access code in Bluetooth packets is not encrypted. Next, the header<br />

in the Bluetooth packet is also not encrypted. The reason for this is also pretty obvious<br />

when you consider that the header contains the address of the destination device. This<br />

www.newnespress.com

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!