Talk:KeeLoq

message: Can someone please correct the pictures in a nice way? I am currently traveling, don't have the time to do it. Bit 16 is supposed to be added linearly during encryption and bit 15 during decryption (see my C source code or the official documentation). I apologise for this error. Ruptor 09:22, 6 June 2007 (UTC)
replies: text: There's another error in the pictures. The first input bit to the NLF is supposed to be bit 1 instead of bit 2 of the NLFSR in encryption, and bit 0 instead of bit 1 in decryption. This error is also in your C source code. Sisyphos2000 21:48, 7 June 2007 (UTC)
replies: text: I have fixed my source code. It's true. One of the bits was off. Ruptor 13:01, 7 September 2007 (UTC)

text: I have also fixed the pictures. Whoever edited them before had merely changed the font and the shape of the arrows, but forgot to fix the most important thing - the cipher structure. The new pictures match 100% my source code and the official decryption.pdf document. I apologize again for these errors. Ruptor 16:08, 15 October 2007 (UTC)
thread_title: Error in the pictures

message: The NLFSR feedback function is 0x3A5C742E. What does this mean? --Abdull 10:36, 9 March 2007 (UTC)
replies: text: It's F(a,b,c,d,e) = d ⊕ e ⊕ ac ⊕ ae ⊕ bc ⊕ be ⊕ cd ⊕ de ⊕ ade ⊕ ace ⊕ abd ⊕ abc. A binary function of N variables can be represented as a 2^N value where each bit in each position represents the value of the output and the position itself is the set of input bits. Basically, it's a 5-to-1 look-up table. See Nicolas Courtois paper for clarification. Ruptor 16:21, 9 March 2007 (UTC)
thread_title: NLFSR

message: Is there a list of car makes/models that use the KeeLoq system?
The Wired article Researchers Crack KeeLoq Code for Car Keys states that Honda, Ford, General Motors, Mercedes Benz and Jaguar use this system.  Many readers, such as myself, are curious as to whether cars that I own (or cars owned by my family members) use this system, so that we may evaluate the risks of using the remote keyless entry and other advanced car-features.  —Preceding unsigned comment added by 128.173.14.24 (talk) 17:37, 4 September 2007 (UTC)
thread_title: Is there a list of car makes/models that use the KeeLoq system?

message: Hello, I am employed in a position where I work with KEELOQ on a daily basis. In response to claims from Bogandov, et, al. In the interests of security concerns from customers and shareholders I have been assigned to a project to test the so-called "slide attack" on real-world KEELOQ applications. I have been working on this since late 2008.
The first thing I did was take Ruptor's code and compile it in Borland C++ 5.0.2. Ruptor's code, which is directly derived from the drawings on this wikipedia article, does not generate the correct cryptographic output. The code I myself wrote in C, however, does, as I am decrypting the output of my own RKE products, on a PC, and correctly so. Ruptor's code, whilst appearing correct on the surface, generates different decrypted data for the same key and same encrypted input and is therefore of no value to me.
I have also examined the encoder chip itself and tried various attacks on the HCS301 encoder, which has not yielded much results, except in that I can prevent overwriting of the encryption key using controlled power glitches, but I am powerless to prevent mass erasure, so it is reasonable to conclude that, sort of deep probing the chip surface, the HCS301 is secure enough on its own.
Miyukisan782 (talk) 07:16, 25 February 2009 (UTC)
replies: text: Thanks for the update - please let us know if you publish your results so that we can reference them here.  Failing that, your input must unfortunately be treated as OR.  Socrates2008 (Talk) 07:25, 25 February 2009 (UTC)
thread_title: Algorithm incorrect

message: Just an observation, but it seems as though this article may have a POV or at least does not give the full story, in that it says nothing about Keeloq 3 technology  —Preceding unsigned comment added by 12.231.151.254 (talk) 14:45, 7 October 2009 (UTC)
thread_title: KeeLoq 3?

message: Hi, some time ago I developed an implementation of KeeLoq in C and in assembly language of Atmel microcontroller (much faster than C on the 8-bit MCUs) and also 
routines in C language which implement the wireless receive/transmit according to the KeeLoq datasheet, and also the programming of HCS Keeloq chips.
I published this code recently under GPL and I thought it might be useful for people interested in Keeloq (since google did not reveal anything equivalent), so I added here an external link (http://www.pittnerovi.com/jiri/hobby/electronics/keeloq/index.html).
However, somebody removed it quickly as "spam". I never contributed to wiki before, so I wonder what is wrong with such a link, which in my opinion
leads to a bigger amount of useful and relevant information than for example the existing external link to Ruptor's implementation in C.
Jiri  —Preceding unsigned comment added by 147.231.28.95 (talk) 15:18, 20 October 2009 (UTC)
thread_title: Keeloq implementation for Atmel microcontrollers

message: Let's say you want to open a garage door without the knowledge and consent of the owner. You set up listening equipment aimed at the location where the owner will be when locking the garage. And you set up a jamming device aimed at the receiver of the garage door opener, such that it will not jam your listening equipment. So he tries to close the door. If you choose to jam all his attempts to close the door, the owner may get suspicious. If you only jam the first attempt and let him close the door on the second attempt, the receiver will no longer recognize the first code you intercepted. Neither of these situations are ideal.
The trick is:
# The owner tries to close the door. Jam it and intercept the code
# The owner tries again to close the door. Jam it again and intercept the code. Immediately close the door by replaying the first code you intercepted.
# When the owner leaves, use the second code to open the door.
-- Nic Roets (talk) 20:14, 1 January 2014 (UTC)
thread_title:  How to properly exploit the replay attack 

message: Hello fellow Wikipedians,
I have just added archive links to  on KeeLoq. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive https://web.archive.org/20120722105616/http://cryptolib.com/ciphers/keeloq/ to http://cryptolib.com/ciphers/keeloq
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
Cheers.—cyberbot IITalk to my owner:Online 12:05, 19 February 2016 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified one external link on KeeLoq. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20070423090909/http://www.keeloq.boom.ru:80/decryption.pdf to http://www.keeloq.boom.ru/decryption.pdf
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 16:03, 31 December 2016 (UTC)
thread_title:  External links modified