0mega
New Member
Hello,
I was thinking about how unsecure wireless remote controls are... Most remote controllers are simple one-way devices that transmit a frequency / code to a car to open it. Anyone with a wideband recorder/playback system can "listen in" and repeat the code to open your car.
My idea works very much like modern-day network logins:
1. Client (remote) sends "want to login" token
2. Server(garage/car/whatever) sends random 16-bit hash.
3. Client XORs the hash with the 16-bit login code and sends it back to server.
4. Server unhashes (XOR again) to extract code
5. Compare codes
6. If codes match, open door / whatever.
Of course, this makes for a clunki(er) remote, but it is far more secure. Simply repeating the code will have no effect at all.
Of course, if my idea is complete ********, feel free to tell me.
Cheerz,
JB
I was thinking about how unsecure wireless remote controls are... Most remote controllers are simple one-way devices that transmit a frequency / code to a car to open it. Anyone with a wideband recorder/playback system can "listen in" and repeat the code to open your car.
My idea works very much like modern-day network logins:
1. Client (remote) sends "want to login" token
2. Server(garage/car/whatever) sends random 16-bit hash.
3. Client XORs the hash with the 16-bit login code and sends it back to server.
4. Server unhashes (XOR again) to extract code
5. Compare codes
6. If codes match, open door / whatever.
Of course, this makes for a clunki(er) remote, but it is far more secure. Simply repeating the code will have no effect at all.
Of course, if my idea is complete ********, feel free to tell me.
Cheerz,
JB