1 / 8

SecurDisc

SecurDisc. Mt Fuji Meeting May 8th, 2007. Nero action items SecurDisc. Use cases ( 6.5 ) SecurDisc in comparison with other protection mechanism ( 6.6 ) LBA relocation on rewritable media ( 6.7 ). 1. Use cases. Copy Protection Content is bound to the physical disc

ronni
Download Presentation

SecurDisc

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SecurDisc Mt Fuji Meeting May 8th, 2007

  2. Nero action items SecurDisc • Use cases (6.5) • SecurDisc in comparison with other protection mechanism (6.6) • LBA relocation on rewritable media (6.7)

  3. 1. Use cases • Copy Protection • Content is bound to the physical disc • Protection made on a file basis • Data can only be read from original disc by SecurDisc licensed application, no copy allowed • Access Control • Password protected • Protects privacy of data • Copy Protection and Access Control • Combines both methods • Data (files) can only be viewed on original disc by entering a password, but not copied

  4. 1.1 Copy Protection

  5. 1.2 Access Control

  6. 1.3 Copy Protection and Access Control

  7. 2. Comparison of protection mechanism • Table of protection mechanism for recordable media types

  8. 3. LBA relocation on rewritable media • As the encryption and decryption of the user data with the LBA and the DUID is performed by the host, it doesn’t matter to what physical location the sector content is written on the disc. In case the host writes data on LBA <n> addressing the LBA in the write command, it will get the same data when reading from LBA <n> addressing the LBA in the read command, even if the sector content is remapped to another physical location on the disc.

More Related