From: lk@mailandnews.com
To: linux-kernel@vger.kernel.org
Subject: CPRM copy protection for ATA drives
Date: 20 Dec 2000 23:23:48 +0000 [thread overview]
Message-ID: <m3lmtazngb.fsf@fork.man2.dom> (raw)
I read this article on theregister today:
http://www.theregister.co.uk/content/2/15620.html
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
such a terrible idea. I imagine that this system is pretty
easy to defeat if you can modify the filesystem. Perhaps even
a ROT13 modification to ext2 would be sufficient?
The consequences of being able to corrupt other people's backups
by introducing "copy-protected" data are intriguing...
Paul
-
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:[~2000-12-20 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 23:23 lk [this message]
2000-12-21 0:54 ` CPRM copy protection for ATA drives Alan Cox
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=m3lmtazngb.fsf@fork.man2.dom \
--to=lk@mailandnews.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.