<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Garage door&#8230; packet sniffer</title>
	<atom:link href="http://hackaday.com/2009/10/03/garage-door-packet-sniffer/feed/" rel="self" type="application/rss+xml" />
	<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/</link>
	<description>Fresh hacks every day</description>
	<lastBuildDate>Fri, 10 Feb 2012 18:08:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: justaguy</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-515573</link>
		<dc:creator><![CDATA[justaguy]]></dc:creator>
		<pubDate>Tue, 22 Nov 2011 05:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-515573</guid>
		<description><![CDATA[I have a security gate opener in my possession that opens the common access gate for apartment complex. The one in my possession belongs to my room mate, and I simply want to dupe it so I can have one too. The homeowners association wants $275 for a new one, fuck that. 

When I open it up and look at the wafer its very simple, but must be using a fixed code as there are no bit switches or interface ports. The plastic case says 418 MHz, the name of the company that issued it, and a sticker with a serial number AND a number marked &#039;Code:&#039;. I&#039;d greatly appreciate advice, it sounds like the people posting here would know. Thank you!]]></description>
		<content:encoded><![CDATA[<p>I have a security gate opener in my possession that opens the common access gate for apartment complex. The one in my possession belongs to my room mate, and I simply want to dupe it so I can have one too. The homeowners association wants $275 for a new one, fuck that. </p>
<p>When I open it up and look at the wafer its very simple, but must be using a fixed code as there are no bit switches or interface ports. The plastic case says 418 MHz, the name of the company that issued it, and a sticker with a serial number AND a number marked &#8216;Code:&#8217;. I&#8217;d greatly appreciate advice, it sounds like the people posting here would know. Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: endersgamer</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-408062</link>
		<dc:creator><![CDATA[endersgamer]]></dc:creator>
		<pubDate>Mon, 20 Jun 2011 19:51:29 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-408062</guid>
		<description><![CDATA[The point of being able to pull off an intrusion like this is that you can really screw someone. Because if there is no sign of forced entry then there is no guarantee that the victims insurance will pay for the theft. Its the same issue that came up when bumpp keys first became prevalent. It screws the person twice because they lose their stuff and then have to pay to replace it ;)]]></description>
		<content:encoded><![CDATA[<p>The point of being able to pull off an intrusion like this is that you can really screw someone. Because if there is no sign of forced entry then there is no guarantee that the victims insurance will pay for the theft. Its the same issue that came up when bumpp keys first became prevalent. It screws the person twice because they lose their stuff and then have to pay to replace it ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-213209</link>
		<dc:creator><![CDATA[Rob]]></dc:creator>
		<pubDate>Tue, 16 Nov 2010 03:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-213209</guid>
		<description><![CDATA[Anyone know where to get the source files? The links are dead]]></description>
		<content:encoded><![CDATA[<p>Anyone know where to get the source files? The links are dead</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mish</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-155695</link>
		<dc:creator><![CDATA[Mish]]></dc:creator>
		<pubDate>Tue, 06 Jul 2010 03:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-155695</guid>
		<description><![CDATA[I was reading a doorking manual and it seemed to me that the remotes for gate entry had to have their five digit code entered into the system and then receive their code to open the gate.  This sounded to me like a wireless router where you can enter the device MAC address.  Wouldn&#039;t this make the sniffed code unusable as you wouldn&#039;t have the correct device number?]]></description>
		<content:encoded><![CDATA[<p>I was reading a doorking manual and it seemed to me that the remotes for gate entry had to have their five digit code entered into the system and then receive their code to open the gate.  This sounded to me like a wireless router where you can enter the device MAC address.  Wouldn&#8217;t this make the sniffed code unusable as you wouldn&#8217;t have the correct device number?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: maya</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-108131</link>
		<dc:creator><![CDATA[maya]]></dc:creator>
		<pubDate>Fri, 20 Nov 2009 02:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-108131</guid>
		<description><![CDATA[Please contact me, I have something to propose you :)]]></description>
		<content:encoded><![CDATA[<p>Please contact me, I have something to propose you :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sunny</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-104591</link>
		<dc:creator><![CDATA[sunny]]></dc:creator>
		<pubDate>Thu, 29 Oct 2009 06:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-104591</guid>
		<description><![CDATA[Or where or how can I build one or buy one. I&#039;ve also heard of people clonning smart key R.F signals for the vehicles that don&#039;t use a key only a R.F transmitter key fob. Any info would love to hear back will always make my job easier.]]></description>
		<content:encoded><![CDATA[<p>Or where or how can I build one or buy one. I&#8217;ve also heard of people clonning smart key R.F signals for the vehicles that don&#8217;t use a key only a R.F transmitter key fob. Any info would love to hear back will always make my job easier.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sunny</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-104589</link>
		<dc:creator><![CDATA[sunny]]></dc:creator>
		<pubDate>Thu, 29 Oct 2009 06:32:27 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-104589</guid>
		<description><![CDATA[Nice I&#039;am a Repo man in colorado need info for scanner R.F transmitter/scanner code grabber for fixed 12 pin security gates. Would love some other type of application for rolling algorithm&#039;s. taw22576@yahoo.com]]></description>
		<content:encoded><![CDATA[<p>Nice I&#8217;am a Repo man in colorado need info for scanner R.F transmitter/scanner code grabber for fixed 12 pin security gates. Would love some other type of application for rolling algorithm&#8217;s. <a href="mailto:taw22576@yahoo.com">taw22576@yahoo.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mel Garage organization</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-99283</link>
		<dc:creator><![CDATA[Mel Garage organization]]></dc:creator>
		<pubDate>Wed, 07 Oct 2009 07:16:33 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-99283</guid>
		<description><![CDATA[Wonderful job. I am unable resist my myself from praising your work. Its among the results of creativity. It educated even me. Now onwards I will keep on observing this blog for such valuable information.]]></description>
		<content:encoded><![CDATA[<p>Wonderful job. I am unable resist my myself from praising your work. Its among the results of creativity. It educated even me. Now onwards I will keep on observing this blog for such valuable information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-99161</link>
		<dc:creator><![CDATA[James]]></dc:creator>
		<pubDate>Tue, 06 Oct 2009 19:33:17 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-99161</guid>
		<description><![CDATA[Not much more I can tell you, the code was done in AVRStudio and the schematic and layout in kicad, I used a standard garage door receiver that receives a 12 bit code, the receiver has active low logic levels. Rest you can get from the code and schematic.]]></description>
		<content:encoded><![CDATA[<p>Not much more I can tell you, the code was done in AVRStudio and the schematic and layout in kicad, I used a standard garage door receiver that receives a 12 bit code, the receiver has active low logic levels. Rest you can get from the code and schematic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bogdan</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-98918</link>
		<dc:creator><![CDATA[bogdan]]></dc:creator>
		<pubDate>Mon, 05 Oct 2009 18:42:52 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-98918</guid>
		<description><![CDATA[hello

i need more information for this device]]></description>
		<content:encoded><![CDATA[<p>hello</p>
<p>i need more information for this device</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shadyman</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-98809</link>
		<dc:creator><![CDATA[Shadyman]]></dc:creator>
		<pubDate>Mon, 05 Oct 2009 01:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-98809</guid>
		<description><![CDATA[@Dave0:

Certain vehicles, like many Chrysler/Dodges, have a system to record and playback 3 different garage door opener codes. The system is called HomeLink (homelink.com).]]></description>
		<content:encoded><![CDATA[<p>@Dave0:</p>
<p>Certain vehicles, like many Chrysler/Dodges, have a system to record and playback 3 different garage door opener codes. The system is called HomeLink (homelink.com).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Skitchin</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-98739</link>
		<dc:creator><![CDATA[Skitchin]]></dc:creator>
		<pubDate>Sun, 04 Oct 2009 17:28:28 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-98739</guid>
		<description><![CDATA[@Zendu: That could be a very useful approach to this-&gt;&quot;The most devastating practical consequence of the side-channel analysis is an attack in which keys can be cloned by intercepting only two messages sent by the legitimate key from a distance of up to 100 metres (330 ft).&quot;]]></description>
		<content:encoded><![CDATA[<p>@Zendu: That could be a very useful approach to this-&gt;&#8221;The most devastating practical consequence of the side-channel analysis is an attack in which keys can be cloned by intercepting only two messages sent by the legitimate key from a distance of up to 100 metres (330 ft).&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M4CGYV3R</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-98707</link>
		<dc:creator><![CDATA[M4CGYV3R]]></dc:creator>
		<pubDate>Sun, 04 Oct 2009 14:20:17 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-98707</guid>
		<description><![CDATA[Nice project, neat setup, but not hardly new. KeeLoq was busted a while back. Here&#039;s the decoding datasheet on it: http://www.keeloq.boom.ru/decryption.pdf]]></description>
		<content:encoded><![CDATA[<p>Nice project, neat setup, but not hardly new. KeeLoq was busted a while back. Here&#8217;s the decoding datasheet on it: <a href="http://www.keeloq.boom.ru/decryption.pdf" rel="nofollow">http://www.keeloq.boom.ru/decryption.pdf</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-98692</link>
		<dc:creator><![CDATA[James]]></dc:creator>
		<pubDate>Sun, 04 Oct 2009 12:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-98692</guid>
		<description><![CDATA[I actually wanted to add transmit capability but there just wasn&#039;t enough room on the chip so I had to remove it. I&#039;m busy with v2 based on the atmega88 which has a number of extra features including saving codes etc.

I&#039;m also gonna try my hand at rolling code systems and whatever else I can find, these are the most common here so that&#039;s why I started with them.

For anyone interested in the keeyloq hack check out the ccc conference from last year, it&#039;s a pretty entertaining watch.

Speech overview:
http://events.ccc.de/congress/2008/Fahrplan/events/3030.en.html

Conference Recordings (#3030):
http://events.ccc.de/congress/2008/wiki/Conference_Recordings]]></description>
		<content:encoded><![CDATA[<p>I actually wanted to add transmit capability but there just wasn&#8217;t enough room on the chip so I had to remove it. I&#8217;m busy with v2 based on the atmega88 which has a number of extra features including saving codes etc.</p>
<p>I&#8217;m also gonna try my hand at rolling code systems and whatever else I can find, these are the most common here so that&#8217;s why I started with them.</p>
<p>For anyone interested in the keeyloq hack check out the ccc conference from last year, it&#8217;s a pretty entertaining watch.</p>
<p>Speech overview:<br />
<a href="http://events.ccc.de/congress/2008/Fahrplan/events/3030.en.html" rel="nofollow">http://events.ccc.de/congress/2008/Fahrplan/events/3030.en.html</a></p>
<p>Conference Recordings (#3030):<br />
<a href="http://events.ccc.de/congress/2008/wiki/Conference_Recordings" rel="nofollow">http://events.ccc.de/congress/2008/wiki/Conference_Recordings</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Prof Plum</title>
		<link>http://hackaday.com/2009/10/03/garage-door-packet-sniffer/comment-page-1/#comment-98643</link>
		<dc:creator><![CDATA[Prof Plum]]></dc:creator>
		<pubDate>Sun, 04 Oct 2009 08:01:09 +0000</pubDate>
		<guid isPermaLink="false">http://hackaday.com/?p=16399#comment-98643</guid>
		<description><![CDATA[@dosman
KeeLoq being &quot;broken&quot; does not entirely mean that it is insecure.

For the rolling codes used in rke for key fobs and garage door openers, there are three valid attacks: First, a side-channel attack which requires physical access and works mostly on pre-1996 devices.  Second, a birthday paradox-based attack to attempt to guess the correct slot for the rolling codes (works relatively well as the code space is ~64K, and with a valid code window of 16 we AT MAX have to try ~4K codes).  Third, jam the signal to prevent the car from locking.  None of these are really that fantastic of a break.

In any of these cases, that is alot of work to do when a good-sized rock through the window will get you into the car just as effectively.

The real break has to do with STEALING cars.  For almost all cars manufactured in the last decade, the keys have a tiny .5&quot;x.25&quot;x.1&quot; rfid-type micro in them.  The car sends this micro a random 32-bit plaintext and the micro responds with a 32-bit cyphertext, if the cyphertext is valid, the immobilizer releases.  The break occurs if a third party sends the micro 65536 plaintexts and receives the resulting cyphers back (takes ~1hr).  Then, using a cluster it is usually possible to get the encryption key from this (you have a ~65% chance of success).  Additionally, some manufactures obtain the encryption key from combining a model-specific manufacturer&#039;s code with the serial # from the key (the micro will give the serial # up if you ask it).  If this is the case for the key you cracked, then you can obtain the manufacturer&#039;s code, and get the encryption key for all other cars of this model just by asking the micro what its serial # is.  Once you are around the immobilizer, you now need a way to start the car (photographic reproduction of a key, bump keys, hot-wiring the ignition, etc).  Note - this method works for some rki systems as well.]]></description>
		<content:encoded><![CDATA[<p>@dosman<br />
KeeLoq being &#8220;broken&#8221; does not entirely mean that it is insecure.</p>
<p>For the rolling codes used in rke for key fobs and garage door openers, there are three valid attacks: First, a side-channel attack which requires physical access and works mostly on pre-1996 devices.  Second, a birthday paradox-based attack to attempt to guess the correct slot for the rolling codes (works relatively well as the code space is ~64K, and with a valid code window of 16 we AT MAX have to try ~4K codes).  Third, jam the signal to prevent the car from locking.  None of these are really that fantastic of a break.</p>
<p>In any of these cases, that is alot of work to do when a good-sized rock through the window will get you into the car just as effectively.</p>
<p>The real break has to do with STEALING cars.  For almost all cars manufactured in the last decade, the keys have a tiny .5&#8243;x.25&#8243;x.1&#8243; rfid-type micro in them.  The car sends this micro a random 32-bit plaintext and the micro responds with a 32-bit cyphertext, if the cyphertext is valid, the immobilizer releases.  The break occurs if a third party sends the micro 65536 plaintexts and receives the resulting cyphers back (takes ~1hr).  Then, using a cluster it is usually possible to get the encryption key from this (you have a ~65% chance of success).  Additionally, some manufactures obtain the encryption key from combining a model-specific manufacturer&#8217;s code with the serial # from the key (the micro will give the serial # up if you ask it).  If this is the case for the key you cracked, then you can obtain the manufacturer&#8217;s code, and get the encryption key for all other cars of this model just by asking the micro what its serial # is.  Once you are around the immobilizer, you now need a way to start the car (photographic reproduction of a key, bump keys, hot-wiring the ignition, etc).  Note &#8211; this method works for some rki systems as well.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

