linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: riel@conectiva.com.br, James Simmons <jsimmons@transvirtual.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] DRM OS
Date: Thu, 13 Dec 2001 09:33:28 -0600 (CST)	[thread overview]
Message-ID: <200112131533.JAA51038@tomcat.admin.navo.hpc.mil> (raw)

Rik van Riel <riel@conectiva.com.br>:
> 
> On Wed, 12 Dec 2001, James Simmons wrote:
> 
> > Microsoft patents loading a trusted OS into a trusted CPU. The OS prevents
> > untrusted applications from accessing Rights Managed Data.
> 
> I haven't looked up the link, but this sounds suspiciously like
> what UNIX permission bits have been doing since the 1970s.
> 
> I guess MS trying to enforce their patent against anyone would
> just get it invalidated, or the claim is narrow enough that
> people can work around it.
> 
> > http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=/netahtml/search-adv.htm&r=1&f=G&l=50&d=CR99&S1=5,892,900.UREF.&OS=ref/5,892,900&RS=REF/5,892,900
> 
> Then again, this only applies to people unlucky enough to live
> in the US. No need to worry.

Besides, there are several technical flaws in the patent itself. First
and formost is that it isn't new (check the Orange book on trusted computer
systems and object reuse). It doesn't include the memory controled by
peripherals - graphics frame buffers and device cache buffers - (the TSEC
object reuse specifications do).

It doesn't even include controlling access to the "trusted OS".

If it did, then owners/users would no longer be able to apply any of the
hundreds of patches such a system (if from M$) would require...:-)

Never mind having access to a "trusted time server" by a disconnected laptop.

Or defining what happens under a power failure...

I wouldn't expect this to last even a first challenge, as long as the
governments own documents were presented as "prior art".

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

             reply	other threads:[~2001-12-13 15:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13 15:33 Jesse Pollard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-13 14:21 [OT] DRM OS Thomas Hood
2001-12-13  4:00 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
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

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=200112131533.JAA51038@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=jsimmons@transvirtual.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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).