SecuROM

» see securom.com as it lived, on the wayback machine

~ the eulogy ~

securom was the drm i remember most directly from spore. ea shipped spore on 7 september 2008 with a securom layer that authenticated online and capped activations at three machines per product key, the player community noticed within hours and the response was the kind of mass-scale rejection that the publisher had not really priced for. wikipedia records spore as the most user-redistributed game of 2008 with roughly 1.7 million bittorrent downloads, which was an honest mark of how badly the activation policy had landed.

to be honest, the brand was older than the spore moment, sony dadc had been developing securom since '98 as a cd-pressing-side anti-copy layer parallel to safedisc. for some reason it sat in the second-tier position behind safedisc through the early '00s and then moved into the lead role as ubisoft and the broader publisher pool walked away from starforce in '06 (close enough). that was a brief window where securom was the new-title default for the western publisher tier and the install-limit pattern that defined its reputation became the industry standard.

the long decline started in '09 when disney removed the protection from tron: evolution as part of the license wind-down, the title later became unplayable on steam when the activation servers stopped responding. sony dadc discontinued the development tools in 2014. microsoft's august '15 windows 10 update blocked the securom driver alongside the safedisc one for the same kernel-driver security disclosure, and the brand stopped being a viable new-title choice by the late '10s.

~ the dossier ~

~ what it was ~

this part is the kind of thing an engineering student in ankara would actually look at, because the protection layered a pressed-disc signature with an online activation check that polled a sony server at install time and at launch. back then. the install-count counter was kept server-side, the player's machine reported a fingerprint of the hardware as a machine id, the server returned an approve-or-deny on whether the activation was within budget. that was the architecture that the player tier collided with on spore.

to be honest, the install limits were not new to securom, the bioshock launch in '07 had a two-install limit that ea raised to five after the manual printed the wrong support phone number and players could not reach activation to get their second install back. mass effect on pc shipped initially with a ten-day reactivation requirement that ea also pulled before launch after the player response. the install-counter pattern was the part of the protection that the publisher tier kept walking into the same complaint about, and securom was the technical mechanism that enforced it.

~ the spore moment ~

in september '08 spore launched with securom and the three-install cap, the amazon product page received an organized one-star review campaign within forty-eight hours, the press wrote about the activation policy more than about the game. for whatever reason that became the canonical reference point for what securom was, even though the technical drm was the same as what had been shipping on smaller titles for a year. a class-action filed by a maryland resident named melissa thomas in september '08 was the legal pressure on top of the press pressure.

to be honest, the spore install policy got raised first to five and then was eventually walked back to a much looser model after the lawsuit settled. the install-counter as a default ea pattern was past by '11 or so, the publisher tier had learned the lesson that capping activations on a single-player game was a fight not worth picking. the technical protection kept shipping on other titles for a few years but the install-count enforcement got dialed back to the point of irrelevance on most catalogs.

~ the long tail ~

the 2014 sony dadc decision to stop developing the tooling was the soft death. the existing protected catalog kept running on existing machines, the new-title business migrated to steamworks and to ea's own origin platform for the games that ea wanted to control end-to-end. the kernel-driver removal from windows 10 in august '15 broke a chunk of the late-'00s catalog the way the parallel safedisc removal did, the support forums for bioshock and the sims series filled with the same kind of no-cd workaround threads.

the disney license expiry on tron: evolution in '19 was the most visible single-title casualty, the game was pulled from steam because the activation servers had stopped responding and the title was no longer launchable. for some reason that one became the example people reach for when they want to talk about the long-term cost of ship-with-drm policies. several other late-'00s securom titles had quiet patches pushed by their publishers to strip the protection from the install before the same thing happened to them.

in '26 securom is past as a brand but not as a footprint, the protected catalog from the '07-to-'12 window sits on collector shelves and steam libraries with the patched-out versions, the bittorrent-era no-cd workarounds remain documented for the titles whose publishers did not patch them. the lesson the industry took out of the spore moment, that a single-player game cannot ship with a tight install counter without losing more sales than the protection saves, became the unwritten rule of the period that followed.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »