From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: lk@mailandnews.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: CPRM copy protection for ATA drives
Date: Thu, 21 Dec 2000 00:54:07 +0000 (GMT) [thread overview]
Message-ID: <E148tzm-0002KI-00@the-village.bc.nu> (raw)
In-Reply-To: <m3lmtazngb.fsf@fork.man2.dom> from "lk@mailandnews.com" at Dec 20, 2000 11:23:48 PM
> Does anyone have any details on this? I presume that the drive
> firmware is capable of identifying copy-protected data during
> a write. I also presume that nobody on lkml would condone
It seems to be very similar to the DVD stuff, including ideas for play once
only blocks and the like. Pay per read hard disk...
> such a terrible idea. I imagine that this system is pretty
> easy to defeat if you can modify the filesystem. Perhaps even
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.
> The consequences of being able to corrupt other people's backups
> by introducing "copy-protected" data are intriguing...
I'm just waiting for a few class action law suits against drive manufacturers
when people's backup tools cannot cope
-
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 prev parent reply other threads:[~2000-12-21 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 23:23 CPRM copy protection for ATA drives lk
2000-12-21 0:54 ` Alan Cox [this message]
2000-12-22 20:03 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2001-01-02 22:41 Rob Landley
2001-01-02 22:46 ` Andre Hedrick
2001-01-02 23:53 ` Rob Landley
2001-01-03 0:15 ` Andre Hedrick
2001-01-03 2:27 ` Erik Mouw
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=E148tzm-0002KI-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@mailandnews.com \
/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