RE: [oss4lib-discuss] (no subject)
Brought to you by:
dchud
From: Karen C. <kc...@kc...> - 2004-06-05 23:43:47
|
Actually, I'm referring to MPEG-21 Part5, in combination with NGSCB. It is worth getting at least a little hysterical about. NGSCB and MPEG-21/5 together do equal DRM, and I am quite sure that's what M$ intends to do. Note that M$ and Time Warner recently became majority owners in a company called ContentGuard, which is the company that holds the patents on the rights expression language in MPEG-21 (and that claims to hold patents on the very IDEA of RELs). That M$ is teaming up with Hollywood shows that they very much intend to be the DRM solution for digital media. Even their own press releases hype that. kc On Sat, 2004-06-05 at 12:58, Matthew J. Dovey wrote: > I presume what you are refering to is the Microsoft Next Generation > Secure Computing Base (also mistakenly referred to as Palladium). > Despite the hysteria in the press, this isn't strictly speaking anything > to do with DRM, in the same way that Public Key Encryption isn't > anything to do with DRM (i.e. you can use the NGSCB to implement DRM in > the same way that you can use Public Key Encryption to implement DRM). > > The main components of NGSCB is a mini-operating system - the idea being > that a small OS can be easier to debug/avoid security flaws. It works > with new hardware so that the host operating system (i.e. Windows > Longhorn) is bypassed for keyboard input and video display (i.e. trojans > running in the insecure OS cannot capture key presses or screen scrape). > The other component of the hardware is a key store, so that you can > encrypt such that it can only be decrypted on that machine, or sign data > so that it could only be signed on that machine (that's the bit which > could be used in DRM, but has many other uses). The key store is also > used for signing agents that are allowed to run in the mini-OS (ala Java > app signing) - the end user can control what agents they allow to run > (i.e. it isn't hardcoded to only run MS stuff). > > Currently Microsoft plans to release the source code of the NGSCB for > general review (i.e. taking on board the opensource philosophy that peer > review of code eliminates security bugs) - although they aren't > releasing the code as opensource (at least they aren't currently > planning to). > > Matthew > > > > -----Original Message----- > > From: oss...@li... > > [mailto:oss...@li...] On > > Behalf Of Karen Coyle > > Sent: Friday, June 04, 2004 6:11 PM > > To: Chuck Bearden > > Cc: OSS4Lib OSS4Lib > > Subject: Re: [oss4lib-discuss] (no subject) > > > > It won't have to be mandated by law. It's being developed my > > Microsoft. > > It'll be mandated by monopoly. > > > > kc > > > > On Fri, 2004-06-04 at 08:42, Chuck Bearden wrote: > > > Bcc: > > > Subject: Re: [oss4lib-discuss] open source bios > > > Reply-To: > > > In-Reply-To: <1086292847.6107.107.camel@kc.kchome> > > > > > > If development of this BIOS works out, it will at least provide a > > > viable alternative to the DRM'd BIOS, if it ever comes to that. > > > > > > Nonetheless, if people perceive that what they gain by > > using computers > > > with built-in DRM is greater than what they give up, the > > DRM'd systems > > > could become very popular even if they aren't mandated by law. > > > > > > Chuck > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the new InstallShield X. > >From Windows to Linux, servers to mobile, InstallShield X is the one > installation-authoring solution that does it all. Learn more and > evaluate today! http://www.installshield.com/Dev2Dev/0504 > _______________________________________________ > > > oss...@li... > > > https://lists.sourceforge.net/lists/listinfo/oss4lib-discuss > see also http://oss4lib.org/ -- ------------------------------------- Karen Coyle Digital Library Specialist http://www.kcoyle.net Ph: 510-540-7596 Fax: 510-848-3913 -------------------------------------- |