www.makemkv.com

Greetings,

MKB20_v77_Venom-_The_Last_Dance_C268

This has been submitted. I have also shared the dump file on my Google drive for Keydb.


Regards,

Greetings,

This title now rips using the latest Keydb file. Thanks!


Regards,

Also submitted this Dump File for Venom: The Last Dance
MKB20_v77_Venom-_The_Last_Dance_2F94.tgz

Latest keydb.cfg does not work. New release, just arrived. Log submitted.

MKB20_v77_Venom-_The_Last_Dance_2F94.tgz
Thanks

Still waiting on MKB20_v77_Venom-_The_Last_Dance_2F94 to get into keydb
Any idea how long the dumps take to process?

The keydb and the MakeMKV internal hashed keys are different things. If you sent your dump to MakeMKV's email address, then it'll get added to the MakeMKV hashed keys. That can take anywhere from 0 to 365+ days (usually a couple weeks on average). If you want it in the public keydb, which may be faster, you'd need to provide your dump file either as an attachment or a link.

archalien wrote: ↑

Wed Jan 22, 2025 1:40 pm

Still waiting on MKB20_v77_Venom-_The_Last_Dance_2F94 to get into keydb

There are two such disks in KEYDB now: Could either of them be yours?

Submitted MKB20_v77_VENOM_THE_LAST_DANCE_C268.tgz

Also submitted "MKB20_v77_Venom-_The_Last_Dance_3B8E.tgz" for the Venom Last Dance 4k Steelbook from Amazon.

I suspect those may be for the BR and the 4k of a different region or such.

Just tried again and still no volume key found although we have 2 people indicating they submitted dumps for this in this thread already.

archalien wrote: ↑

Wed Jan 22, 2025 8:27 pm

I suspect those may be for the BR and the 4k of a different region or such.

No, they're definitely both UHD disks. Are you sure you've put your KEYDB.cfg file in the correct directory? It needs to go where MakeMKV writes its TGZ dump files. That's in your case.

archalien wrote: ↑

Wed Jan 22, 2025 8:27 pm

I suspect those may be for the BR and the 4k of a different region or such.

Just tried again and still no volume key found although we have 2 people indicating they submitted dumps for this in this thread already.
...

The 0x9349DF8D2340B840DEF34E009A3D86423EE76CEE entry corresponds to the C268 variant. I'm not sure about the other entry but it also probably doesn't match your 2F94 disc.

In order for your 2F94 variant to be added to the public keydb you or someone else will need to either attach or post a link to a suitable dump file.

Remember, the folks associated with the public keydb are entirely distinct from the MakeMKV team who receive/process dumps sent to their email account.

Footfungus07 and Clarkss12 both posted ~1week ago they submitted dumps for 2F94 prior to me joining the topic.

SamuriHL's post post just confused the heck out of me.....
My ignorant understanding (and most likely flawed) was that the private key(s) have been known for a while, but to keep police from showing up on doors, they are not shared/packaged publicly. Instead, dumps are collected and processed against the PK, the decode key is then added o one or more magical lists in the cloud. Or so I assumed, as makemkv is able to unlock new titles without a new version of the software, so I expected it was phoning home/or to a shared db of keys.

So I dont understand the distinction between the keydb and internal hashed keys SamuriHL is referring to, the public list vs the makemkv private list. Or how the process differs for each. Im only aware of submitting the dump to makemkv. Im always willing to learn something new if anyone who knows can correct me/fill in the gaps in my knowledge.

Over the years many/most new movies (a little less with back catalog re-releases) where decryptable on day one, owning to a disc walking out of the factory "for the scene" or falling out of the back of a bestbuy distribution truck *cough*.

Im trying to tease apart if 2 people sent in bad dumps, the are in the 1-365+ day queue, they where not sent to the "faster" method SamuriHL indicated. If the key there and I have some other problem.

Any education here appreciated. Thx

keydb_helper wrote: ↑

Thu Jan 23, 2025 2:17 am

archalien wrote: ↑

Wed Jan 22, 2025 8:27 pm

I suspect those may be for the BR and the 4k of a different region or such.

Just tried again and still no volume key found although we have 2 people indicating they submitted dumps for this in this thread already.
...

The 0x9349DF8D2340B840DEF34E009A3D86423EE76CEE entry corresponds to the C268 variant. I'm not sure about the other entry but it also probably doesn't match your 2F94 disc.

In order for your 2F94 variant to be added to the public keydb you or someone else will need to either attach or post a link to a suitable dump file.

Remember, the folks associated with the public keydb are entirely distinct from the MakeMKV team who receive/process dumps sent to their email account.

You're overcomplicating this.

Keydb is a public database of keys maintained by anyone who has the ability to submit keys. Typically that is done using findvuk but for UHD that method only finds the unit keys. Makemkv requires the vuk in order to decrypt a disc. Some entries in the public keydb contain the full entry including the vuk. Those entries are added by people who likely have some kind of processing key to be able to calculate the vuk. That's why posting a dump as an attachment or a link sometimes helps get a full entry into the public keydb faster.

Makemkv requires you to send the dump via email. Mike clearly has his own processing key and is able to calculate the vuk. That then gets added to what Mike calls the hashed keys, and makemkv downloads that assuming it can reach the makemkv update server. This process takes as long as it takes Mike to process the dumps he receives in email. This is completely separate from the public keydb.

Sent from my SM-S928U1 using Tapatalk

Thanks SamuriaHL

I think my general understanding was accurate, you filling in some additional details helped!
For the first time I looked up keydb and how to use it w/ makemkv, the disc opened/ripped!

I saw in the data dir the private data tar, it was last modified on 1/8, does that contain the hashed keys?
If it did, it would/could possibly explain why the key for this disc was not yet available.
Not needed but would be nice to know if that statement is accurate.

Thx