Security of Advanced Access Content System: Difference between revisions

Revision as of 08:49, 12 August 2017

Revision as of 14:50, 11 September 2017

Line 88:

| last = Block

| first = Ryan

| url = httphttps://www.engadget.com/2007/01/20/blu-ray-cracked-too/

| title = Blu-ray cracked too?

| date = 2007-01-20

Line 139:

|date=2007-05-02

|work=[[Forbes]]

|url=httphttps://www.forbes.com/technology/2007/05/02/digital-rights-management-tech-cx_ag_0502digg.html

|accessdate=2007-05-04|archiveurl=https://web.archive.org/web/20070504173353/http://www.forbes.com/technology/2007/05/02/digital-rights-management-tech-cx_ag_0502digg.html|archivedate=2007-05-04}}</ref>

Both sites' administrators eventually decided to allow publication of the key.<ref>{{cite web

Line 175:

|url=http://www.freedom-to-tinker.com/?p=1155#comment-367359

|title=You Can Own an Integer Too

|accessdate=2007-06-09}} [httphttps://web.archive.org/web/20070824092116/http://www.freedom-to-tinker.com/?p=1155#comment-367359 Archived copy of page] (original link dead)</ref>

The use of encryption does not offer any true protection against memory snooping, since the software player must have the encryption key available somewhere in memory and there is no way to protect against a determined PC owner extracting the encryption key (if everything else fails the user could run the program in a [[virtual machine]] making it possible to freeze the program and inspect all memory addresses without the program knowing).