Rolling code

"Hopping code" redirects here. For other uses, see frequency-hopping spread spectrum.

A rolling code (or sometimes called a hopping code) is used in keyless entry systems to prevent a simple form of replay attack, where an eavesdropper records the transmission and replays it at a later time to cause the receiver to 'unlock'. Such systems are typical in garage door openers and keyless car entry systems.

Techniques

• Common PRNG (pseudorandom number generator) — preferably cryptographically secure — in both transmitter and receiver
• Transmitter sends 'next' code in sequence
• Receiver compares 'next' to its calculated 'next' code.
• A typical implementation compares within the next 256 codes in case receiver missed some transmitted keypresses.

HMAC-based one-time password employed widely in multi-factor authentication uses similar approach, but with pre-shared secret key and HMAC instead of PRNG and pre-shared random seed.

Application in RF remote control

A rolling code transmitter is useful in a security system for improving the security of radio frequency (RF) transmission, comprising an interleaved trinary bit fixed code and rolling code. A receiver demodulates the encrypted RF transmission and recovers the fixed code and rolling code. Upon comparison of the fixed and rolling codes with stored codes and seeing that they pass a set of algorithmic checks, a signal is generated to actuate an electric motor to open or close a movable component.

Rolling code vs. fixed code RF remote control

Remote controls send a digital code word to the receiver. If the receiver determines the codeword is acceptable, then the receiver will actuate the relay, unlock the door, or open the barrier. Simple remote control systems use a fixed code word; the code word that opens the gate today will also open the gate tomorrow. An attacker with an appropriate receiver could discover the code word and use it to gain access sometime later. More sophisticated remote control systems use a rolling code (or hopping code) that changes for every use. An attacker may be able to learn the code word that opened the door just now, but the receiver will not accept that code word for the foreseeable future. A rolling code system uses cryptographic methods that allow the remote control and the receiver to share codewords but make it difficult for an attacker to break the cryptography.

KeeLoq

HCS301 chip from an Audi A6 keyless entry remote, which uses a rolling code system

Main article: KeeLoq

The Microchip HCS301 was once the most widely used system on garage and gate remote control and receivers. The chip uses the KeeLoq algorithm. The HCS301 KeeLoq system transmits 66 data bits:

• 34 bits are not encrypted: a 28-bit serial number, 4 bits of button information, and 2 status bits (repeat and low battery indicators).
• 32 bits are encrypted (the rolling code): 4 bits of button information, 2 bits of OVR (used to extend counter value), 10 bits of DISC (discrimination value; often the low 10 bits of the serial number), and a 16-bit counter. In a resyncing situation, the encrypted 32 bits are replaced with a 32-bit seed value.

As detailed at KeeLoq, the algorithm has been shown to be vulnerable to a variety of attacks, and has been completely broken.

Rolljam vulnerability

A rolling code transmitted by radio signal that can be intercepted can be vulnerable to falsification. In 2015, it was reported that Samy Kamkar had built an inexpensive electronic device about the size of a wallet that could be concealed on or near a locked vehicle to capture a single keyless entry code to be used at a later time to unlock the vehicle. The device transmits a jamming signal to block the vehicle's reception of rolling code signals from the owner's fob, while recording these signals from both of his two attempts needed to unlock the vehicle. The recorded first code is forwarded (replayed) to the vehicle only when the owner makes the second attempt, while the recorded second code is retained for future use. Kamkar stated that this vulnerability had been widely known for years to be present in many vehicle types, but was previously undemonstrated. A demonstration was done during DEF CON 23.

External links

• How Remote Entry Works; cites successful attack on KeeLoq.
• Atmel Inc.'s application note AVR411