On Thu, Jul 04, 2002 at 11:29:08AM +0200, Cees de Groot wrote:
> The problem with DRM inside your CPU is that your CPU will refuse to be part
> of a non-trusted computing base. Which will mean that it will not load a BIOS
> that hasn't got the right sig, the BIOS will not load a OS boot block that
> hasn't got the right sig, etcetera up to the application. So if you don't get
> Squeak signed by Micro$oft (or whoever will control the signing keys for
> Palladium), Squeak will simply refuse to run on your Windows platform.
> Similarly, Linux will not load, until you run the single copy of the kernel
> that has been Palladium-certified (which, in turn, will only run signed
> binaries, i.e. - no Squeak). 
this is not entirely correct - the cpu is supposed to be completely able
to run non-trusted software. with the small drawback that other
DRM-crippled^Wenabled hardware will refuse to do some of their jobs,
like decoding video (as in a non-trusted environment there could be an
app getting the stuff out of video memory)

so even linux may still run, with crippled hardware...

patrick mauritz
-- 
,------------------------------------------------------------------------.
>             Moonlight 3D Resurrected | www.moonlight3d.net             <
`------------------------------------------------------------------------'
            do what thou whilst shall be the whole of the law
                     love is the law, love under will
                there is no law beyond do what thou whilst
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20020707/3b3c1eff/attachment.pgp