" Starting from version 1.10.9 MakeMKV supports additional key format, called “hashed keys”. It is unknown to me that anyone used the file-name "keydb.cfg" for hashed-key format keyfile! It's about converting hashed key to non-hashed key format in makemkv (optional feature).Īnd AnyDVD could use the non-hashed-key waY, when reintgrating back key.txt file which is same as keydb.cfg, see other posts I know that hashed-key probably is better and that AnyDVD doesn't/didn't support it with keys.txt, I'm talking about the keydb.cfg, is that a non-hashed key format or not?ĪnyDVD accepts keydb.cfg (so I'd guess it's not hashed key format!)ĭoes makemkv have a hash key to non-hash-key file converter or not?
It's all confusing, as AnyDVD implemented this file format feature, and people could use it to fed AnyDVD with it for decryption.Īnd afaik it seems to me that there was no other decryption information part involved from AnyDVD at that time (maybe).Ĭlick to expand.That is not the issue I'm talking about. To me it looked like makemkv was doing format-processing (not involving a keysdb.cfg list from known older discs)Īnd is the other hash/VUK part or whatever needed for decrypting still missing in keysdb.cfg from makemkv? Well makemkv can convert hashed key to keysdb.cfg, can it not? What is the disadvantage of preserving "keys.txt" (even if older format type) ? I didn't say anything at all that the new OPD support for UHD was bad. Well I'd find it handy to preserve keys.txt in AnyDVD.
The affected user just needs to use hashed-key to keysdb.cfg-converter from makemkv. If makemkv has the hashed key for ones UHD-disc, but AnyDVD should not (maybe) occasionally, Keysdb.cfg It still compatible to AnyDVD 8.2.1.7. Maybe this is because AnyDVD removed "key.txt" support.
0 kommentar(er)
