Doom9's Forum - View Single Post - Ultra HD Blu-ray

dizzier · 15th September 2016, 19:17

I have bought BH16NS55 and Deadpool UHD Blu-Ray disc.

First, some impressions about the drive. Yes, it can read UHD Blu-Ray. Deadpool is a two layer UHD disc with 33GB per layer. There are also three layer discs, with the same data density, like Batman vs. Superman, but I haven't tested that (will not spend money on that piece of crap). While it reads UHD discs, it is kinda unreliable. From time to time it simply refuses to work and returns various errors. Usually reloading the disc fixes the problem, but one time I had to power it down, otherwise it refused to work at all. I was able, on the second try, to make image of Deadpool disc with data transfer not leaving 10-20MB/s range. It might be just an unreliable disc, I don't have a second one yet. The drive does not support AACS 2.0, so it almost surely will not work with software players, if they become available.

Now onto AACS 2.0, which is more interesting. The overall disc structure seems the same. UHD disc does not contain BD+ (normal Blu-Ray counterpart is BD+). It does have bus encryption enabled, which seems mandatory for AACS 2.0.
The MKB file has the same basic structure like those from AACS 1.0. It reports itself as a MKBv60. It has a new type and several new record types with unknown purpose. It is signed with a different AACS LA certificate, which was expected. Host and driver revocation lists are exactly the same like those found on normal Blu-Ray MKBv60 discs. This makes sense, as drives would need to maintain only a single list of host certs to revoke (AACS 2.0 certificates use longer keys, but the certificate ID space seems shared). The subset-difference tree seems to be much larger, instead of usual 562 entries there are now 181250 (number of C-values record entries to be precise).

I've tried running AACS 1.0 auth for this disc. Surprisingly... it was successful. I was able to read VID, PMSN and Read Data Key (used by bus encryption). Now, onto some speculation why it works and what does it mean.
My guess is that AACS 1.0 drives are not supposed to read UHD discs. Both VID and PMSN are simply some values store on disc, that are not accessible in normal way. Drive is perfectly able to read them, but reading is protected by AACS-authentication process, which requires host certificate. If we assume that AACS 2.0 stores those values at the exactly the same place as AACS 1.0, then AACS 1.0 drive, capable of reading UHD discs, will gladly read them, provided AACS 1.0 host certificate. Bus encryption is somewhat different, (some) disc sectors have some low level markers that tell the drive to encrypt them on the fly. Getting the decryption key from the drive also requires AACS-authentication. If the same markers are used by AACS 2.0 (I don't see why not, it is kinda low level thing) then AACS 1.0 drive will handle this perfectly fine, if it can read the disc. Which we know it can

If the above is correct, then it means that this kind of drive kinda defeats part of AACS 2.0. But, don't get your hopes too high. The values (VID, etc.) I was able to retrieve could be completely bogus. Also, to fully decrypt AACS 2.0 we would need device/processing/volume key. There were no new device/processing keys available even for AACS 1.0 for a few years and we don't have any player/ripper to extract volume key from.

Disc information:

Code:

Disc ID: F58AA868C40D5894C332F9BDB978522432D5CC82
VID    : 55F4D4B1F77D26D0E7A9D55DA5599AA7
MKBv   : 60
PMSN   : will not provide for obvious reasons, but was able to read it
Bus encryption:
  Device support:   yes
  Enabled in media: yes
Content Certificate ID: 006F8005EF00
BD-J Root Cert hash:    0000000000000000000000000000C73B53981817
Device binding ID:      some random value generated by my PC
Host Revocation List  (MKB version 60):
  000000000001 - 0000000003e8
  000080000001 - 0000800080e8
  270f80000001 - 270f80000bb8
  ff2210100001 - ff221010001f
  ff2210400001 - ff221040001f
  ff2220000001 - ff22200000ff
  ff2290100001 - ff229010001f
  ff2290400001 - ff229040001f
  ff22a0000001 - ff22a00000ff
  ff2318000001 - ff231800001f
  ff2318100001 - ff231810001f
  ff2318400001 - ff231840001f
  ff2340000001 - ff23400000ff
  ff2710000001 - ff271000001f
  ff2790000001 - ff279000001f
  ffff0000000b - ffff00000014
  ffff00000016
  ffff00000021 - ffff0000002a
  ffff00000035 - ffff00000038
  ffff0000004e - ffff00000052
  ffff00000054 - ffff00000057
  ffff0000005d - ffff00000066
  ffff00000080
  ffff00000088 - ffff00000091
  ffff00000094
  ffff000000ae
  ffff000000b2 - ffff000000bb
  ffff000027db
  ffff00002817
  ffff00002820
  ffff00002834 - ffff0000283d
  ffff00002846
  ffff0000284b
  ffff80000001 - ffff80000024
  ffff80000029
  ffff8000002f
  ffff80000039
  ffff80000045
  ffff80000071
  ffff80000079
  ffff8000007c - ffff8000007e
  ffff800000ad
  ffff800000c4 - ffff800000c6
  ffff800000d0
  ffff800000f4 - ffff800000fd
  ffff80000146
Drive Revocation List  (MKB version 60):
  000000000001 - 0000000003e8
  000080000001 - 0000800055f0
  270f20000001 - 270f20000514
  270f80000001 - 270f800007d0
  ff2600000001 - ff2600000096

15th September 2016, 19:17	#16 \| Link
dizzier Registered User Join Date: Jan 2010 Posts: 74	I have bought BH16NS55 and Deadpool UHD Blu-Ray disc. First, some impressions about the drive. Yes, it can read UHD Blu-Ray. Deadpool is a two layer UHD disc with 33GB per layer. There are also three layer discs, with the same data density, like Batman vs. Superman, but I haven't tested that (will not spend money on that piece of crap). While it reads UHD discs, it is kinda unreliable. From time to time it simply refuses to work and returns various errors. Usually reloading the disc fixes the problem, but one time I had to power it down, otherwise it refused to work at all. I was able, on the second try, to make image of Deadpool disc with data transfer not leaving 10-20MB/s range. It might be just an unreliable disc, I don't have a second one yet. The drive does not support AACS 2.0, so it almost surely will not work with software players, if they become available. Now onto AACS 2.0, which is more interesting. The overall disc structure seems the same. UHD disc does not contain BD+ (normal Blu-Ray counterpart is BD+). It does have bus encryption enabled, which seems mandatory for AACS 2.0. The MKB file has the same basic structure like those from AACS 1.0. It reports itself as a MKBv60. It has a new type and several new record types with unknown purpose. It is signed with a different AACS LA certificate, which was expected. Host and driver revocation lists are exactly the same like those found on normal Blu-Ray MKBv60 discs. This makes sense, as drives would need to maintain only a single list of host certs to revoke (AACS 2.0 certificates use longer keys, but the certificate ID space seems shared). The subset-difference tree seems to be much larger, instead of usual 562 entries there are now 181250 (number of C-values record entries to be precise). I've tried running AACS 1.0 auth for this disc. Surprisingly... it was successful. I was able to read VID, PMSN and Read Data Key (used by bus encryption). Now, onto some speculation why it works and what does it mean. My guess is that AACS 1.0 drives are not supposed to read UHD discs. Both VID and PMSN are simply some values store on disc, that are not accessible in normal way. Drive is perfectly able to read them, but reading is protected by AACS-authentication process, which requires host certificate. If we assume that AACS 2.0 stores those values at the exactly the same place as AACS 1.0, then AACS 1.0 drive, capable of reading UHD discs, will gladly read them, provided AACS 1.0 host certificate. Bus encryption is somewhat different, (some) disc sectors have some low level markers that tell the drive to encrypt them on the fly. Getting the decryption key from the drive also requires AACS-authentication. If the same markers are used by AACS 2.0 (I don't see why not, it is kinda low level thing) then AACS 1.0 drive will handle this perfectly fine, if it can read the disc. Which we know it can If the above is correct, then it means that this kind of drive kinda defeats part of AACS 2.0. But, don't get your hopes too high. The values (VID, etc.) I was able to retrieve could be completely bogus. Also, to fully decrypt AACS 2.0 we would need device/processing/volume key. There were no new device/processing keys available even for AACS 1.0 for a few years and we don't have any player/ripper to extract volume key from. Disc information: Code: Disc ID: F58AA868C40D5894C332F9BDB978522432D5CC82 VID : 55F4D4B1F77D26D0E7A9D55DA5599AA7 MKBv : 60 PMSN : will not provide for obvious reasons, but was able to read it Bus encryption: Device support: yes Enabled in media: yes Content Certificate ID: 006F8005EF00 BD-J Root Cert hash: 0000000000000000000000000000C73B53981817 Device binding ID: some random value generated by my PC Host Revocation List (MKB version 60): 000000000001 - 0000000003e8 000080000001 - 0000800080e8 270f80000001 - 270f80000bb8 ff2210100001 - ff221010001f ff2210400001 - ff221040001f ff2220000001 - ff22200000ff ff2290100001 - ff229010001f ff2290400001 - ff229040001f ff22a0000001 - ff22a00000ff ff2318000001 - ff231800001f ff2318100001 - ff231810001f ff2318400001 - ff231840001f ff2340000001 - ff23400000ff ff2710000001 - ff271000001f ff2790000001 - ff279000001f ffff0000000b - ffff00000014 ffff00000016 ffff00000021 - ffff0000002a ffff00000035 - ffff00000038 ffff0000004e - ffff00000052 ffff00000054 - ffff00000057 ffff0000005d - ffff00000066 ffff00000080 ffff00000088 - ffff00000091 ffff00000094 ffff000000ae ffff000000b2 - ffff000000bb ffff000027db ffff00002817 ffff00002820 ffff00002834 - ffff0000283d ffff00002846 ffff0000284b ffff80000001 - ffff80000024 ffff80000029 ffff8000002f ffff80000039 ffff80000045 ffff80000071 ffff80000079 ffff8000007c - ffff8000007e ffff800000ad ffff800000c4 - ffff800000c6 ffff800000d0 ffff800000f4 - ffff800000fd ffff80000146 Drive Revocation List (MKB version 60): 000000000001 - 0000000003e8 000080000001 - 0000800055f0 270f20000001 - 270f20000514 270f80000001 - 270f800007d0 ff2600000001 - ff2600000096 Last edited by dizzier; 15th September 2016 at 19:48.