linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: aaronl@vitelus.com (Aaron Lehmann)
Cc: andre@linux-ide.org (Andre Hedrick),
	jsimmons@transvirtual.com (James Simmons),
	linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: [OT] DRM OS
Date: Tue, 18 Dec 2001 16:17:19 +0000 (GMT)	[thread overview]
Message-ID: <200112181617.fBIGHJQ16815@pinkpanther.swansea.linux.org.uk> (raw)
In-Reply-To: <20011214163235.A17636@vitelus.com> from "Aaron Lehmann" at Dec 14, 2001 04:32:35

> On Fri, Dec 14, 2001 at 01:15:48AM -0800, Andre Hedrick wrote:
> > CPU(crypto)<->Memory(crypto)<->Framebuffer(crypto)
> > ata(clean)<->diskcontroller(crypto)<->Memory(crypto)<->CPU(crypto)
> > scsi(crypto)<->diskcontroller(crypto)<->Memory(crypto)<->CPU(crypto)
> > CPU(crypto)<->Bridge(crypto)<->Memory(crypto)
> > 
> > Just watch and see!
> 
> Why would crypto help at all?

So you cant tap the data anywhere. 

Think

encrypted music fed to an encrypted audio controller to speakers which
decrypt and add watermarks

encrypted video decrypted and macrovision + watermarked only in buffers
the CPU cant access

audio input that has legally mandated watermark checks and wont record
watermarked data.

That is the dream these people have. They'd also like the OS to scan for
"illicit" material and phone the law if you do, and to have a mandatory
remote shutdown of your box

(and if you read the MS media player license anyone who agrees to it signed
up to that)

Alan


  parent reply	other threads:[~2001-12-18 18:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13  4:00 [OT] DRM OS James Simmons
2001-12-13  4:07 ` Matt
2001-12-13 13:38 ` Rik van Riel
2001-12-14  9:15 ` Andre Hedrick
2001-12-15  0:32   ` Aaron Lehmann
2001-12-17  6:10     ` TimO
2001-12-18 16:17     ` Alan Cox [this message]
2001-12-18 18:54       ` James Simmons
2001-12-18 19:06         ` Andre Hedrick
2001-12-18 19:53       ` Aaron Lehmann
2001-12-18 20:05         ` Dave Jones
2001-12-18 20:10           ` Aaron Lehmann
2001-12-18 20:25             ` Dave Jones
2001-12-18 20:45               ` H. Peter Anvin
2001-12-19 10:39               ` Helge Hafting
2001-12-18 20:44             ` Rik van Riel
2001-12-18 20:56               ` Gábor Lénárt
2001-12-19 21:49                 ` Thomas Dodd
2001-12-20 22:40             ` Marco Ermini
2001-12-21 16:38               ` Brendan Pike
2002-01-02 22:13     ` Chris Friesen
2002-01-02 22:30       ` Alan Cox
2002-01-03  1:52       ` Andre Hedrick
2002-01-03 11:10         ` Henning P. Schmiedehausen
2001-12-13 14:21 Thomas Hood
2001-12-13 15:33 Jesse Pollard

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=200112181617.fBIGHJQ16815@pinkpanther.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=aaronl@vitelus.com \
    --cc=andre@linux-ide.org \
    --cc=jsimmons@transvirtual.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).