In the beginning every (still) camera had the same keys - life was easy: you could unlock with that pair or the "reset pair". Then they started throwing different C/R pairs at us... (game on! :-)) So, BillW added the pv2keys.txt mechanism to PV2Tool as a way to accumulate and use found keys. The theory - then - was that they were using a limited set of C/R key pairs and if we just collected them all then we'd be able to unlock any camera. As far as I know... we never found any duplicate key pairs in the still cameras. Also, IIRC the "line app" that PD posted in 2006 generated a new key pair from random numbers for each camera. That makes sense from a security angle. The processing station knows the C -> R algorithm and can, thus, unlock any key pair. It's more secure if PD puts a totally different C/R pair in each camera - repeating pairs is subject to our "collect them all" attack approach. So, I'm sorta surprised that they're not generating a separate pair for each device - maybe that became too much work somewhere along the way??

maybe they thought that just using a pad they can discard is more secure than using a crypto algorithm that can be discovered and broken .

Where are there repeats?

They all requested their own responce, and fawkes.effigy retrieved them and posted as such.

more than one person has used the same key, iirc. i could be wrong, though. i think we should check this. maybe i'll get my 53.14 and try it. it's somewhere at my house

brandonuOisin, Key 38 worked for your cam, but had you posted your challenge before? Just wondering if they are reusing 09 keys already... oisinNo brandonu, I didn't want to beg for keys. Rolling Eyes But one of the ones that fawkes.effigy supplied worked on one of my two 53.14s so they have to be using duplicates, how else could fawkes.effigy retrieve the response to a challange that was never even posted??

I stand corrected....but I see it as only a mistake. I doubt there will be more. Either way there is no harm in starting a 09 responce thread.

Duplicates or not? Proof of repeats? I searched through this thread looking for number 38 and could not find it! I also looked for number 37 and it wasn't here either. Perhaps those requests were in other threads. I will not believe there is a duplicate unless someone can identify the source of the challenge on these forums. If the source lives near Oisin then I would assume that after not being able to unlock the camcorder they took it back and Oisin somehow managed to get the return. For anyone that believes there is a duplicate - please provide a link to the original post by someone else of Oisin's 09 challenge. I do have an open mind - if as I previously speculated concerning the 09s only being on new 53.14 camcorders and the return to 04s on 53.18s then there is a possibility that flash chips are now being mass produced with a minimal set of keys. However if that is the case I doubt they would have used more than a dozen. Either fawks.effigy works for CVS, has access to a recycling machine, knows a CVS manager, is a Pure Digital employee who believes in "1 2 many 4 all", or has broken the algorithm. Willing to pay? How about a penny for the guy? ...thus the match is lit. Anyone care to speculate on meaning of those words?

No, I'm not kize, but I traded cams with kize in May or so.... Never went back to see if he had posted his/her key request. :oops: I'm sure that must be the C that f.effigy generated the R key from. I'm just 'ol Oisin. :roll: snogeez's twin. Thanks again to my favorite British antihero. btw...

I don't recall the burning of any effigies in V for Vendetta, just some Guy Fawks masks and some shiny knives. So is our response key poster going to burn like straw from a lit match; or blow his own dead body up in a train. Willing to pay? How about a penny for the guy? ...thus the match is lit. With Bonfire night just a few nights away I'm anxious as to what will become of the Guy (worth plenty of pennies I hope).

Requesting a response for: S YourNameHere C 0980a5b8f0255ce3be0bf862823d2ab704729b74e1e275aa305824a566895ed6 C 77a460113e2a7bf91f00d0b8ebc358f3035b27fcc1d3f14a1367cd2769df39a9 C d21c5ee361f1965cd6342cc17a1463d64bacb9b259d96c2c70493e91f7d57598 C 181127972221b4f62bce94e4f9d9534a238ed9fd739def388f26ff49d8131b8a R 0980a5b8f0255ce3be0bf862823d2ab704729b74e1e275aa305824a566895ed6 R 77a460113e2a7bf91f00d0b8ebc358f3035b27fcc1d3f14a1367cd2769df39a9 R d21c5ee361f1965cd6342cc17a1463d64bacb9b259d96c2c70493e91f7d57598 R 181127972221b4f62bce94e4f9d9534a238ed9fd739def388f26ff49d8131b8a Camera revision retrieved from camcorder: 53.14 Thank you :) Edit: Oops! forgot the firmware version