Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

Mobile

Testing Security and Association for Certified Wireless USB


After this initial association, the device and host will communicate wirelessly without the cable. Cable association is considered highly secure because the user must have physical control of the devices in order to attach the cable. In addition, the connection context is exchanged "out-of-band" (not over the air) making eavesdropping virtually impossible.

Numeric Association
In the numeric association model, devices associate without using a wired cable, but require the user to confirm the association by verifying a code number manually. After locating a nearby wireless USB host, the device may show a short code number on its display, which the user will then verify with the host.

The specification also has provisions for devices that do not have input capabilities. In this case, the host simply displays the number and the user clicks "OK," if it matches. Alternately, hosts can require the user to enter a predefined code number supplied with the device, a method familiar to users of many existing wireless technologies today. Any of these methods establish a connection context similar to that obtained in the cable association model.

Security and encryption
Once association is complete using either of these two methods, the devices are now authorized to communicate using the connection context that is established during the association process. During each session, the devices will initially derive a "session" key (also called a "pair-wise temporal key" or PTK) which is based on the pre-established connection context.

Wireless traffic between devices is encrypted using the session key, and therefore any receiver, including any analysis tools, must have prior knowledge of the connection context in order to determine the session key and decrypt the wireless traffic. However if the connection key is known, the analysis tool can determine the session key by listening in to the wireless traffic as the devices begin to communicate.

Analyzing secure traffic
Protocol layer testing for wireless technologies generally involves a radio-based "sniffer" to eavesdrop on the exchange between devices. Analysis tools must perform this task with minimal impact on the real-world operating environment of the devices. The WiMedia specifications do not require encryption of the PHY and MAC header information. This allows devices (and analysis tools) to identify framing and routing information even if the packets are encrypted. But all certified wireless USB logical data transfers will be encrypted.

LeCroy's protocol analysis platforms are designed to address this security problem. For devices that use the cable association model, an integrated plug-in for capturing the cable association sequence is available.

It automatically records and passes the connection context to the radio-based analysis engine contained within the analyzer. The analyzer radio channel can then automatically follow the 4-way handshake and use the connection context to derive the "session" key (or PTK). With this unique session key in the hardware-recording engine, the analyzer can automatically decrypt the scrambled wireless traffic.

Support for the Numeric Association model is provided through a software interface that allows the user to manually enter the connection context for paired devices.

In both cable and numeric association, the pairing information is preserved in non-volatile memory. This allows the test tool to automatically recognize when these devices establish future connections and automatically derive a new PTK whenever a new 4-way handshake exchange takes place between the devices.

Important points:

  • The session keys are regenerated every time the two devices power up. The analyzer must be powered on and record the 4 way handshake sequence at this stage to automatically derive the PTK and decrypt the scrambled traffic.
  • In some cases, developers can use a diagnostic key (CK= 0) for debug environments. But most validation labs will require testing with commercial products using real CK values.
  • In the Numeric model, the user must enter the Connection Host ID and the Connection Key in the analyzer software for a given device. The CK is generally a known value that is pre-programmed in firmware (but is never transmitted over the air).
  • If a host-device pair have already established a connection context using a cable association model prior to the introduction of the analyzer, it will be necessary to repeat the cable association while monitoring the USB traffic between the host and the device in order for the analyzer to capture the connection context.

Testing of both the association process and the security process will be required to gain certification of wireless USB devices. This will be enforced through the USB-IF certification program, which will allow companies to test device and host compliance to all Certified Wireless USB specifications.

About the author
Mike Micheletti is the Wireless USB Product Manager at LeCroy's Protocol Solutions Group.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.