1. 18 Dec, 2013 1 commit
  2. 13 Dec, 2013 1 commit
  3. 11 Dec, 2013 1 commit
  4. 24 Oct, 2013 1 commit
  5. 20 Oct, 2013 5 commits
  6. 08 Oct, 2013 2 commits
  7. 07 Oct, 2013 5 commits
    • npzacs's avatar
      Erase sensitive data in close · 5bde0423
      npzacs authored
    • Janusz Dziemidowicz's avatar
      Fix reading PMSN · 9ad1cd75
      Janusz Dziemidowicz authored
      While working on bus encryption I've found out that some drives (if
      not all) require a new AACS-Auth for reading data keys. It seems that
      the same goes for reading PMSN. After digging through my discs I've
      finally found one with PMSN and I was able to verify this with two LG
      drives. Fix it by moving PMSN reading to a separate function with a
      new AACS-Auth.
    • npzacs's avatar
    • npzacs's avatar
      Dropped support for compile-time PATCHED_DRIVE flag. · 91bda6ce
      npzacs authored
      If this is still needed, it should be implemented as run-time option (environment variable ?).
    • Janusz Dziemidowicz's avatar
      Support for AACS bus encryption · 583df16f
      Janusz Dziemidowicz authored
      Due to the fact that AACS bus encryption was only hinted by early AACS
      specification there seems to be some misconceptions.
      First, what bus encryption is _not_:
      - it does not encrypt all communication between drive and host
      - it does not encrypt VID retrieval
      - it does not use bus key (this is only poor wording in the
      Second, what is required for bus encryption to be activated:
      - a bus encryption capable drive, drive certificate will have 0x01 as
        a second byte
      - a bus encryption capable disc, content certificate (located in
        AACS/Content000.cer) will have 0x80 as a second byte
      - a bus encryption capable host, host certificate will have 0x01 as a
        second byte
      There are various combinations of all of those flags, so let's provide
      a short summary:
      - if drive is not bus encryption capable, then bus encryption will not
        be used, other flags are not relevant and normal AACS procedure will
        work as usual
      - if drive is bus encryption capable but disc is not bus encryption
        enabled then bus encryption will not be used; however, drive will
        only allow hosts with bus encryption capable certificates, without
        one normal VID retrieval will fail, but getting VID from other
        source will make the disc playable
      - if drive is bus encryption capable and disc is bus encryption
        enabled then bus encryption will be used, only hosts with bus
        encryption capable certificates can read such discs; getting VID
        from other source is not enought to read such disc as one must also
        have Read Data Key to decrypt bus encryption which is drive specific
      While most of the current drives are supposed to be bus encryption
      capable, most of the discs currently are not and it is quite hard to
      come across one. Obviously this might change in the future.
      So what is encrypted by bus encryption? Excatly the same data that is
      encrypted by normal AACS, this means .m2ts files located in
      BDMV/STREAM directory. Only this and nothing else. Bus encryption is
      applied on the fly by the drive. Since the disc is already AACS
      encrypted the host must first decrypt bus encryption and then perform
      normal AACS decryption. So what is the difference? Bus encryption uses
      encryption key that is drive specific, this means that the same disc
      read on another drive model will produce differently encrypted
      data. Without bus encryption, files simply copied from disc can be
      decrypted if one gets proper VID. With bus encryption, such copy is
      useless, unless proper decryption key is retrieved from the exact same
      model of the drive. I am not sure if the encryption key is specific to
      the drive model or every drive unit will have a different one.
      This and several previous commits implement everything that is needed
      to support bus encryption:
      - determining if bus encryption is enabled from certificates
      - retrieval of read data key that is used to encrypt data
      - proper decryption (bus encryption works on sector boundary) before
        main AACS decryption
      Code was tested with mplayer on LG BH16NS40 with "The Alien Anthology
      Archives" disc from Alien Anthology (it is the only bus encryption
      enabled disc out of 6 in the anthology).
  8. 13 Sep, 2013 2 commits
    • npzacs's avatar
      mmc: cache drive certificate · 53fd3ed2
      npzacs authored
      All drives do not support REPORT_KEY with format 0x38, so we need to
      cache the certificate from aacs authentication procedure.
    • Janusz Dziemidowicz's avatar
      Retrieve bus encryption flags from drive and content certificate · 7c8c7b43
      Janusz Dziemidowicz authored
      For bus encryption to be active it must be enabled both by the drive
      and the disc.
      Drive certificate contains Bus Encryption Capable (BEC) flag in the
      least significant bit in the second byte of the certificate.
      Content certificate contains Bus Encryption Enabled (BEE) flag in the
      most significant bit in the second byte of the certificate.
      Retrieve both bits so it is now possible to check if bus encryption is
      active (it will not be active if the disc does not enable it, even on
      bus encryption drive; most discs currently do not enable it).
  9. 12 Sep, 2013 3 commits
  10. 04 Jul, 2013 2 commits
  11. 23 Jun, 2013 1 commit
  12. 04 Mar, 2013 1 commit
  13. 04 Jan, 2013 1 commit
  14. 16 Aug, 2012 3 commits
  15. 11 Aug, 2012 1 commit
  16. 04 May, 2012 3 commits
  17. 25 Apr, 2012 2 commits
  18. 18 Feb, 2012 5 commits