Since MakeMKV doesn't contain any BD+ keys it requires either generic or disc-specific SVQ file to process BD+ protected disc. In that regard disc-specific SVQ files are very similar to AACS volume keys. They share the same fate as AACS processing keys though - once published the keys contained in generic SVQ would be revoked and will stop working with newer discs.ĭisc-specific SVQ only allow processing of a single specific disc, but they last forever and provide no revocation information. Generic SVQs allow processing of all BD+ discs that were released before specific date - they are similar to what is an AACS processing key. SVQ files come in two flavors - generic SVQs and disc-specific SVQs. SVQ file is a small (typically less than 64 bytes) file that contains keys necessary to execute BD+ program. MakeMKV contains an implementation of BD+ virtual machine that is required to execute BD+ code and can process any BD+ enabled disc, however there is a big catch - MakeMKV doesn't contain BD+ decryption keys. Two things are required in order to execute BD+ program - execution environment (BD+ virtual machine ) and a set of decryption keys.

BD+ program code must be executed in order to access protected AV clips in addition to being encrypted AV clips are also 'damaged' and BD+ code execution is required to 'fix' the files. Every blu-ray player knows how to execute such program and program code has complete access to all player hardware. In addition to standard AACS encryption each disc with BD+ protection contains a program that is executed by a player each time disc is loaded. An overview of BD+ (albeit somewhat incorrect) can be found at wikipedia. BD+ is a sophisticated protection scheme used by some blu-ray discs.

Makemkv blu ray forum