# rolling code and garage door openers

**URL:** <https://boards.straightdope.com/t/rolling-code-and-garage-door-openers/654545>\
**Category:** Factual Questions\
**Created:** [April 1, 2013, 4:25pm UTC](https://boards.straightdope.com/t/rolling-code-and-garage-door-openers/654545 "2013-04-01T16:25:37Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![LSLGuy](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/lslguy/32/5813_2.png) [@LSLGuy](https://boards.straightdope.com/u/LSLGuy)\
**Post date:** [August 31, 2015, 2:00am UTC](https://boards.straightdope.com/t/rolling-code-and-garage-door-openers/654545/21 "2015-08-31T02:00:25Z")

</div>

As always, xkcd anticipated this by several years: [xkcd: Security](http://xkcd.com/538/)

**Hail Ants** & **beowulff** have it right. This exploit is cute, might well be implementable as \*\*Habeed \*\*explains, but is not really a reason for the whole car remote keyfob and garage door opener industry to go to red alert and replace the entire installed base.

---

<div class="post-metadata">

**Author:** ![ftg](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ftg/32/2801_2.png) [@ftg](https://boards.straightdope.com/u/ftg)\
**Post date:** [August 31, 2015, 9:37pm UTC](https://boards.straightdope.com/t/rolling-code-and-garage-door-openers/654545/22 "2015-08-31T21:37:31Z")

</div>

> [@beowulff](#):
>
> Clearly, the way to defeat this hack is to never allow an out-of-sequence code to work.
> 
> Then, your window of vulnerability is one keypress - if the bad guy captures your code, he must use it before you press your remote again, or his code is invalidated.

Um, see step 3 on my list. People who figure out this stuff are, you know, kind of smart.

[Previous page](https://boards.straightdope.com/t/rolling-code-and-garage-door-openers/654545.md?page=1)