From: Rob Landley <landley@flash.net>
To: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: CPRM copy protection for ATA drives
Date: Tue, 02 Jan 2001 17:41:39 -0500 [thread overview]
Message-ID: <3A525923.330B0482@flash.net> (raw)
> Its probably very hard to defeat. It also in its current form means
> you can throw disk defragmenting tools out. Dead, gone. Welcome to
> the United Police State Of America.
Doesn't anybody remember the days of "dongle keys" on the Commodore 64?
Plug a special circuit into the joystick port in order to use this
program?
And we all remember how the pirates got around this, don't we? The easy
way: crack the program.
This is yet another hardware based copy protection tool like floppy
disks with strategically placed holes burned into them by lasers
(leaving a bad sector you can't reformat away), or cartridge-based
programs that tried to overwrite their own memory address ranges. Or
forcing people to the third word from paragraph two on page ten of the
instruction manual (since the manual is, more or less, hardware.)
Welcome back to the 1980's, they never learn...
There's nothing new under the sun, and the "zero day warez" people never
even broke stride dealing with this sort of thing. All it WILL do is
annoy people who try to legitimately use the system. And, of coruse,
make a lot more people buy SCSI if they sabotage the ATA spec this
way...
What are they going to do installing one of these programs on a
non-compliant drive? (A modern 74 gig drive is likely to last me a
while, you know.) Refuse and limit their potential installed base to
only systems manufactured after 2002? Yeah, people do that kind of
thing all the time (requires MMX), and the products don't last that long
on the shelves, do they?
Has anybody brought up the LEVELS of nested stupidity in this particular
proposal to the committe? (Committee iq: average intelligence of
members, divide by headcount. Nice to see that holds true.)
I'm not particularly alarmed by it, though. Disappointed, yes. But a
market that refused to buy micro-channel architecture, refused to buy
rambus memory, and outright laughed at Microsoft BOB, isn't likely to
let this get shoved down its throat even if it DOES pass as an official
spec. And another advantage Open Source has over proprietary software
(we provide what the users actually WANT, if only 'cause we're the
users. A GPLed program isn't likely to depend on this "feature", is
it? Or the Intel CPU ID...).
Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-02 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 22:41 Rob Landley [this message]
2001-01-02 22:46 ` CPRM copy protection for ATA drives Andre Hedrick
2001-01-02 23:53 ` Rob Landley
2001-01-03 0:15 ` Andre Hedrick
2001-01-03 2:27 ` Erik Mouw
-- strict thread matches above, loose matches on Subject: below --
2000-12-20 23:23 lk
2000-12-21 0:54 ` Alan Cox
2000-12-22 20:03 ` Andre Hedrick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A525923.330B0482@flash.net \
--to=landley@flash.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox