Slashdot Mirror
Sticky Tape Defeats Sony DRM Copy Protection
cybrpnk2 writes "As reported by InformationWeek, Sony BMG Music's controversial copy-protection scheme can be defeated with a small piece of tape. According to thinktank Gartner analysts Martin Reynolds and Mike McGuire, Sony's XCP technology is stymied by sticking a fingernail-size piece of opaque tape on the outer edge of the CD. 'After more than five years of trying, the recording industry has not yet demonstrated a workable DRM scheme for music CDs. Gartner believes that it will never achieve this goal as long as CDs must be playable by stand-alone CD players.'"
Here's what you can do to defeat it without risking your optical drive: Hold shift when inserting the disc or, even better, disable CD autostart. But that wouldn't make such a nice headline, would it?
Last time I had to defeat the usual sort of multi-session CD DRM I just used a whiteboard pen. It's helpful because if you go to far in (and start losing the last track), you can just rub little bits off until you get it just right.
Gotta love it. Almost as cool as the captain crunch whistle.... well, not quite.
... what did you expect, something profound?
How to permanantly turn off CD Autorun on Windows.
Yes, there is. There are a few different versions of this, but the general idea is to intentionally put bad data in the tracks (or the TOC) that would be error-corrected out by an audio CD player, but cause a CD-ROM to fail while attempting to read it. Some modern CD-ROM drives still have trouble with this type of copy control. Since the error correction layers have been subverted, the tiniest scratch will usually render the CD unplayable.
More info here: http://www.cdrfaq.org/faq02.html#S2-4-3
You got it backward: Lotus would not run *unless* it failed to write that spot.
.... 1-2-3 runs
Copy on ordinary floppy --> write works --> 1-2-3 won't run
Original disk --> write fails --> 1-2-3 runs
write-protect disk --> write fails -->
Actually the tape in question was originally invente4d by the military during World War II and called duck tape as water 'rolled off' of it like a ducks back. It was later rechristened as duct tape after the war when it proved valuable for duct repairs as well, so both names are right.
I am Spartacus
For those with XP (and something similar works for 2k)
Disabling AutoPlay
I find it best to disable CD or DVD autoplay in XP using either local group policy or, for an enterprise, an Active Directory group policy.
The local group policy editor method:
* Click Start
* Click Run
* Enter GPEDIT.MSC
Group Policy mmc will popup. On left panel:
* Double-click Computer Configuration to open submenu
* Double-click Administrative Templates to open submenu
* Double-click System to open submenu
* Double-click Turn autoplay off option which will be near the bottom of the list in the right panel.
The default is the Not configured . Set it to Enabled.
This will still allow Windows to regonize when new media is inserted and any icons will appear/update or whatever. You can still right click and choose autoplay, but no CDs or DVDs will autoplay upon insertion. You can also change the setting to do the same with all inserted drives to stop autoplay for usb drives and the like.
//Information does not want to be free; it wants to breed.
Audio CD Protections, in brief:
- Zeroth Generation (the Click Generation):
* Weak Sectors in ATIP: TTR Technologies MusicGuard (never deployed)
Flat out doesn't work at all, you probably wouldn't even notice they'd done anything. Any Lite-On, BenQ or Plextor wouldn't even skip a beat. Only CD-ROM tested which even gave a damn was a Sony (heh), the drive in the PlayStation 1 to be precise. Didn't get a contract, so TTR partnered with Macrovision, and tried harder. Much harder. Much too hard, in fact.
* Weak Sectors causing C2 Errors in Audio: TTR Technology/Macrovision SAFEAUDIO (limited deployment), Settec Alpha-Audio D-Type (data type, never deployed)
Extremely rare, no longer used; the market overwhelmingly rejected it, which is to say, it broke a music exec's speakers. High channel return rate because of obscenely low compatibility, duplicators returning whole batches as bad pressings because they couldn't perform any useful QA on discs deliberately damaged to this extent. Useless. (TTR apparently liquidated.)
Archiving: Alternate CDFS.VXD tools for Win9x may work, as they interpolate in exactly where SAFEAUDIO puts corruption. Other than that, deliberate damage = not perfectly playable, or rippable. Effectively an analogue medium with huge deliberate noise spikes. Use a mint disc, do the best you can, and high-order-interpolate over the scratches (Adobe Audition or something), just like archiving vinyl.
- First Generation (The Anti-CD Generation):
Archiving all first-generation formats merely needs a Good Drive and Good Software with Good Settings. Can be divided into roughly three groups:
* High Jitter Spike: Cactus Data Shield (classic): CDS-100/CDS-200, First4Internet XCP-Aurora XCP "Red"
(0'09", insert bad CIRC sector, 1200 weak sector/desync, 2 *blank* sectors with no sync, then start again with normal data.) Intent: Cause a "hiccup" during a burstmode rip which would be absorbed by a CD player's (tiny) buffer. Reality: Any quality drive firmware, buffer, or jitter correction, means you won't even skip a beat. Might slow down a little, but that's all. Now only marketed for internal releases/promos.
* Malformed TOC/Evil Session with no player: Early Sony key2audio (1.0), Settec Alpha-Audio S-Type (session type), First4Internet XCP-Aurora XCP1
Bread and butter, it's simple; include a normal or malformed TOC, and sprinkle liberally with a seriously malformed second session, relying on CD-ROMs being multisession and CD players being single session only.
* Malformed TOC/Evil Session with autorun player: Sony key2audio, SunnComm MediaClòQ
Differs from the above only in the second session being malformed, but having a valid data track containing a DRMv2 WMA player (or downloader). Players have evil EULAs, and may interfere with ripping while the player is running (although the first version of the key2audio player that appeared actually shifts the session enough to allow flawless ripping while the player is running...!) but as far as known, they don't leave behind malicious software.
- Second Generation (The Autorun Generation):
Rate of returns was still high, so Macrovision tried a weaker system with a much higher false negative, but a much lower false positive. Actually caught on; almost no returns. They could actually put the CD logo on these if they wanted.
* Valid CD-Extra with autorun player: Macrovision CDS-300, Macrovision TotalPlay CD, Alpha-Audio M-Type (main type)
Player (MS-DRMv2, as usual) interferes with ripping (while it's running) but doesn't seem to leave any malicious software behind. If the autorun isn't run (disable it, or hold SHIFT while inserting CD and be careful in Explorer) or supported, it's a normal CD-Extra. First session is valid Red Book.
- Third Generat
regrettably a recent study has shown that the one thing that 'duct' tape is really not good for, is repairing ducts... (heating ducts anyway, the glue melts)
It's apparently good for warts though
-- it's ridiculous how many people misspell ridiculous... (damn, damn, damn...)
Actually it was invented by Johnson & Johnson (http://www.ideafinder.com/history/inventions/duct tape.htm). The military doesn't invent anything, they contract the private sector to develop things for them.
I was also thinking some one should explain to them what the V stand for in DVD.
Well, originally the "V" stood for "Video". That presumably made some marketing guy from some DVD Consortium company that made non-video devices unhappy, so it was renamed to "Versitile". After many more dollars spent debating this crucial issue, nobody could agree, so officially the "V" stands for nothing.
You probably think I'm joking; I assure you, I'm not, sad as it is.
I once had a boss that kept marketing people off of his back by generating busywork to occupy their time. Every time they had a meeting in which they wanted to influence anything technical, he'd bring up the fact that something lacked a name and emphasized how crucial it was to the product's success that the name be appealing. They'd vanish for a month. It was amazing to see this guy in action.
Of course, we had to put up with silly names as a result, but we didn't have to deal with technically broken things, so it was worthwhile.
Any program relying on (nontrivial) preemptive multithreading will be buggy.