Post HD DVD Volume Unique Keys here - post questions in the forum

[Janvitos]

------------------ Message from KenD00 added by moderator

This thread is pretty dead by now, but to honor the work of the people who contributed to it i collected all the keys posted here, corrected the syntactically wrong entries, removed all duplicates and put all remaining ones in one file.

This file is alphabetically sorted after the title and is ready to be used by DumpHD 0.61 or later.

Date of release: 2009-06-03
Number of entries: 282

The file is located here:

http://forum.doom9.org/showthread.ph...66#post1293366

------------------ Original Message from Janvitos

From now on, the list will be posted as an attachment only.
The reason for this is that it exceeded the maximum allowed characters.

Please, everyone who posts keys, post them according to the KEYDB.CFG format.
Updating the key file requires some of my spare time which i don't have in abundance.
You might also consider the fact that if you don't post the hash, the key becomes useless to most.

Here are some examples of GOOD and BAD formats :

GOOD - Formatted According to KEYDB.CFG
F8A5AA1BD29AC9E8E679A90F468912EE33A8E219=House of Wax (GER) |V|10/17/06| 12339EB8200A8143259E52C529D80CC2

BAD - Incorrect Format
Army of Darkness
Hash: 97551320C87D3D240B0D7438A9CC5EA13D7A6F81
Key: A8545372CF7E2D9D12434AB8AC4CB4D0

BAD - Incorrect Format
96628A2FC0C8F28881FD5374A18CBF79590E04B BABEL (US) AA3EFB5F296A36F6F6FD538717693699

BAD - Missing Hash
Assault On Precinct 13 EEE1ADA9B9E0C65312AA09E6A0D4EB73

I understand that some of you are using the xml format which is far from a bad thing.
Unfortunately, I do not have time to convert the 100+ movies KEYDB.CFG file into that format.

Please, take two minutes of your time to correctly format the keys for posting.

Thanks to all.

Janvitos

[Eeknay]

It might be wise to label if the discs are USA/EU/etc origin since there are different versions.

[jlobee]

Apollo 13 (USA) Volume Unique Key: 8BA9C422F93C9B4B4247814530B29C48

Wouldn't it be a good idea to keep an up to date KEYDB.cfg file with all know keys, title+(US/EU/etc) and hashes and attach it each time there's an update.
Ore update it from time to time and always attach the newest version to the original post.

Originally Posted by Eeknay

It might be wise to label if the discs are USA/EU/etc origin since there are different versions.

I think it would be best to post the complete line with hash, title, key and all, exactly as it looks in the KEYDB.cfg file and add info about origin (US/EU/etc.) to the title name.This way it would be ready to copy/paste directly into the KEYDB.cfg file.
So post your keys etc. into code tags just like this:

0000000000000000000000000000000000000000=My movie 1 (US)               |V|MM/DD/YY|   00000000000000000000000000000000

Remember to add US/EU/etc. to the title

Maybe a new KEYDB.cfg format should be created for version 1.01 with a separate field for origin (US/EU/etc.)?

[tonyp12]

Originally Posted by He-Man

Maybe a new KEYDB.cfg format should be created for version 1.01 with a separate field for origin (US/EU/etc.)?

No need, they should have different hash so just treat it as two different titels.

If you want to add the word '(US)' to the title name there is nothing stopping you.

[Eeknay]

Superman Returns (USA) Volume Unique Key: EC2EC7F847F6D304B3C26F121CA578DA

[VistaVick]

Originally Posted by markrb

I am wondering if this violates forum rules.
If IFO information is a violation would these be also?
Just a heads up so you won't be stunned if they decide this way.
Start looking elsewhere to post these if it works out as I think it will.

Mark

It was stated by a mod in another thread that posting these keys would be allowed.

[tonyp12]

Originally Posted by VistaVick

It was stated by a mod in another thread that posting these keys would be allowed.

Probably just so we can experiment for awhile.

But after they get orders from DMCA to stop it will change.
The sponsors for this site does not like to be involved with
shady stuff either.

[jokin]

Originally Posted by tonyp12

0E75082678AAD5CD4410A28A662D6832D21EB325=KING KONG         |V|MM/DD/YY|802F78B1B20D1183638D84E1A96D6EDD
C8A57242AF4CB5C0D7848BDA10821F984DC656E0=Serenity          |V|MM/DD/YY|D075568AE6BB0B3F85446927B3794C28
=SuperMan returns  |V|MM/DD/YY|EC2EC7F847F6D304B3C26F121CA578DA

17C8312A7BEA25A08606F118AD265FD657161D0D=Superman Returns

[evdberg]

Isn't it the idea to exchange MM/DD/YY with the actual month/day/year? No idea what the exact use of this is, but it's a bit silly to keep it like MM/DD/YY.

[tonyp12]

Should we use the date the key was hacked or the date the
movie disc was manufactured?

If the movie is re-released it should have a different hash
so to keep track of if with different date does not seem necessary.

Originally Posted by tonyp12

Should we use the date the key was hacked or the date the movie disc was manufactured?

from FAQ.txt:

Field 4: File creation date
This field is informational only. It's ignored by the program. It should be the creation date of the media file on the disk.

[LoloMc]

Originally Posted by evdberg

Isn't it the idea to exchange MM/DD/YY with the actual month/day/year? No idea what the exact use of this is, but it's a bit silly to keep it like MM/DD/YY.

Originally Posted by tonyp12

Should we use the date the key was hacked or the date the
movie disc was manufactured?

If the movie is re-released it should have a different hash
so to keep track of if with different date does not seem necessary.

IMHO, It is a MUST to use the manufactures date ! (And they could also release collector and no collector disk with different keys)

[Eeknay]

Originally Posted by Janvitos

87A660A656EDD1E07F66DB1A7DE594028A9587E2=V for Vendetta |V|00/00/00| AE196597E6A87A04AE6A24655990A4A6

Are we sure this is confirmed, guys? I found the same key, but the movies EVOs wouldn't decrypt (everything else would)... same thing just happened to Miami Vice, I think UControl and/or IME is screwing it up somehow.

[tonyp12]

Originally Posted by LoloMc

IMHO, It is a MUST to use the manufactures date ! (And they could also release collector and no collector disk with different keys)

No it's not.

If you get hold of two hash/keys sets that show same movie title but different hash and keys,
just add both your keydb file.
backuphddvd will take care of it from there.

[moshmothma]

Originally Posted by Eeknay

Are we sure this is confirmed, guys? I found the same key, but the movies EVOs wouldn't decrypt (everything else would)... same thing just happened to Miami Vice, I think UControl and/or IME is screwing it up somehow.

Kong decrypts and is playable.

[Eeknay]

419D740F2288CEE1EEB60613DAD9D74D7B63203B=Equilibrium (Jap) |V|MM/DD/YY| 343CE9EE7DCB4018AA064BA09FF19B6F

BA3C0208848EA13383F34E9E5BB95BDF0D89F1C8=Red Dragon (USA) |V|MM/DD/YY| 80596E6D9A94D2A3FDB094B9BA2D0A0A

EBC08E19B2059140DFF133E2B953D3A1538D7669=Miami Vice (USA) |V|MM/DD/YY| 3CB25E9C23BED3A496D049B9FCD0915B

A85B0043201474AC56794EA4AAE2C35577752FB3=The Mummy (USA) |V|MM/DD/YY| D6984C6B80D56F96CAE369474345E2B9

A236F74A67CC51270E328F94BC6B4D905A628F9F=Casino (USA) |V|MM/DD/YY| A1DC17F6FA052A4BB4A0D66A7C49DBD9

EDEA3051F5802CB7FF80A24DFE7C720705D36A0F=Mission: Impossible (USA) |V|MM/DD/YY| 10CA125A572A96AE6EB74F6574CCC24D

1DBFD499BC05FB33F14FB76BBDD847B79B190AEA=Mission: Impossible 2 (USA) |V|MM/DD/YY| 8FD8341028A8A300AA16D7F8CCAB7E89

AF4BC7D6A55B08E6175204CABE862ECBB33B1DED=Mission: Impossible 3 (USA) |V|MM/DD/YY| 11D6A8CD59494EF3D4EC4E9002E902F9

NB: Miami Vice + M:i-3 did NOT work for me. The extra features + menus decrypted and played fine in PDVD 6.5, but the main movie files did not. YMMV.

[pyrates]

Oh I knew this day would come

[Albion]

Originally Posted by moshmothma

Kong decrypts and is playable.

Well my ordinary HD-DVD of King Kong plays perfectly using the HD-DVD Drive.Tried to decrypt and test a little of the main feature (5mins) and get very bad stutter.Logos and menu loop etc plays fine although with the HD-DVD Universal logo,it locks up at the end and I have to close PowerDVD down.

Anyone else with this problem? Can I expect to record only a small part of the feature in this way,as a test,without any problems?