Topic on Talk:SecuROM

This page shows the changes between two versions of a post by Mirh in the topic "Plan" on Talk:SecuROM. You can see other versions of this post at its history page.

@@ Line 9: / Line 9: @@
 * somewhat like starforce, they were faulted for what were [https://web.archive.org/web/20211029000802/https://support.securom.com/pop_drakensang.html actually] Windows [https://web.archive.org/web/20081225070222/http://secusphere.com/smf/index.php?topic=6.0 bugs] (even though it did *once* happen it was them to [https://web.archive.org/web/20020727181932/http://nwn.bioware.com/forums/viewforum.html?forum=49 screw up])
-* It was probably once they exhausted every possible "physical trick" to play with DVDs, that they resolved into just strengthening their VM and [https://web.archive.org/web/20080229134513/http://www.tuts4you.com/download.php?list.46 whatnot]. I wonder if Denuvo isn't just the continuation of this, once the "take care yourself of ownership checks" aspect was dropped (anyway tokens and registry keys should be documented)
+* <s>It was probably once they exhausted every possible "physical trick" to play with DVDs, that they resolved into just strengthening their VM and [https://web.archive.org/web/20080229134513/http://www.tuts4you.com/download.php?list.46 whatnot]. I wonder if Denuvo isn't just the continuation of this, once the "take care yourself of ownership checks" aspect was dropped (anyway tokens and registry keys should be documented)</s>
+* [https://xakep.ru/2015/08/07/securom/ actually], the rabbit hole is even deeper: people figured out how to fake the online activation in the first place (known in russian circles as [https://web.archive.org/web/20191024143753/https://xakep.ru/static/re-malware/20_tres.pdf Тибериумный реверсинг], or "Tiberium reversing"). This is why they'd probably better burn down the entire thing and just move to anti-tamper (lucky for them, given in [https://jeyndoe.github.io/edump/pages/action=vthread&forum=13&topic=19719&page=31.html 2017] I tentatively believe something with their old official activation software was leaked)
 * Intel's [https://web.archive.org/web/20160205070308/http://www.intel.com/content/dam/www/public/us/en/documents/specification-updates/desktop-6th-gen-core-family-spec-update.pdf errata doc] isn't of great insight, and anyway they only started to publicly release microcode for Skylake with a hint of a changelog [https://salsa.debian.org/hmh/intel-microcode/-/blob/releases/bpo7/debian/changelog#L239 months later]. After some tinkering though <small><small>(I bisected [https://www.gigabyte.com/Motherboard/GA-Z170X-Gaming-7-rev-10/support#support-dl-bios GA-Z170X-Gaming 7] bios F3 and F4, and found a [https://h30434.www3.hp.com/t5/Notebooks-Archive-Read-Only/SecuROM-8016-error-due-to-Skylake-CPU-needing-microcode/td-p/5394582 clear bug report] placing a tighter lower bound)</small></small> I could at least confirm this fix came with microcode, in either revision 2F if it even exists, or most definitively 3A.
 * there's always that asterisk about older ([https://web.archive.org/web/20010117055800/http://www.cdmediaworld.com/hardware/cdrom/cd_protections_1.shtml#SecuROM oldest]) releases possibly not working for real in modern systems. Is it a myth, or maybe could they employ some DOS/9x/16-bit voodoo? What is the "SecuromVistaVersionLie" ACT shim for? <small>EDIT: [https://github.com/Luca1991/luca1991.github.io/commit/9cd5ea46ee856a1c2994e466c4bea1b1637bc821#comments well], [[Arabian Nights]], [[South Park Rally]] and [[Populous: The Beginning|Populous III]] should be tested I guess. Maybe they relied on DOS interrupts or drivers once upon a time?</small>