[iwar] [fc:Report:.Microsoft.plans.security.chip.for.next.Windows]

From: Fred Cohen (fc@all.net)
Date: 2002-06-24 20:56:11


Return-Path: <sentto-279987-4894-1024977307-fc=all.net@returns.groups.yahoo.com>
Delivered-To: fc@all.net
Received: from 204.181.12.215 [204.181.12.215] by localhost with POP3 (fetchmail-5.7.4) for fc@localhost (single-drop); Mon, 24 Jun 2002 20:58:13 -0700 (PDT)
Received: (qmail 11350 invoked by uid 510); 25 Jun 2002 03:55:01 -0000
Received: from n5.grp.scd.yahoo.com (66.218.66.89) by all.net with SMTP; 25 Jun 2002 03:55:01 -0000
X-eGroups-Return: sentto-279987-4894-1024977307-fc=all.net@returns.groups.yahoo.com
Received: from [66.218.66.97] by n5.grp.scd.yahoo.com with NNFMP; 25 Jun 2002 03:55:07 -0000
X-Sender: fc@red.all.net
X-Apparently-To: iwar@onelist.com
Received: (EGP: mail-8_0_3_2); 25 Jun 2002 03:55:07 -0000
Received: (qmail 63659 invoked from network); 25 Jun 2002 03:55:07 -0000
Received: from unknown (66.218.66.217) by m14.grp.scd.yahoo.com with QMQP; 25 Jun 2002 03:55:07 -0000
Received: from unknown (HELO red.all.net) (12.232.72.152) by mta2.grp.scd.yahoo.com with SMTP; 25 Jun 2002 03:55:07 -0000
Received: (from fc@localhost) by red.all.net (8.11.2/8.11.2) id g5P3uBQ20426 for iwar@onelist.com; Mon, 24 Jun 2002 20:56:11 -0700
Message-Id: <200206250356.g5P3uBQ20426@red.all.net>
To: iwar@onelist.com (Information Warfare Mailing List)
Organization: I'm not allowed to say
X-Mailer: don't even ask
X-Mailer: ELM [version 2.5 PL3]
From: Fred Cohen <fc@all.net>
X-Yahoo-Profile: fcallnet
Mailing-List: list iwar@yahoogroups.com; contact iwar-owner@yahoogroups.com
Delivered-To: mailing list iwar@yahoogroups.com
Precedence: bulk
List-Unsubscribe: <mailto:iwar-unsubscribe@yahoogroups.com>
Date: Mon, 24 Jun 2002 20:56:11 -0700 (PDT)
Subject: [iwar] [fc:Report:.Microsoft.plans.security.chip.for.next.Windows]
Reply-To: iwar@yahoogroups.com
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=3.2 required=5.0 tests=RISK_FREE,FREE_MONEY,DIFFERENT_REPLY_TO version=2.20
X-Spam-Level: ***

Report: Microsoft plans security chip for next Windows
<a href="http://www.infoworld.com/articles/hn/xml/02/06/24/020624hnpalladium.xml">http://www.infoworld.com/articles/hn/xml/02/06/24/020624hnpalladium.xml>


By Peter Sayer  June 24, 2002

MICROSOFT WANTS TO change the fundamental architecture of the PC, adding
security hardware prior to the release of the next generation of its
Windows operating system around 2004, according to a media report. 

The Redmond, Wash.-based company wants future PCs to contain a security
technology called Palladium, and is in discussion with Intel and
Advanced Micro Devices (AMD) to develop the chips, according to a report
in the July 1 issue of Newsweek magazine published Sunday on the MSNBC
Web site.  Microsoft owns a stake in MSNBC. 

Representatives of Intel and Microsoft contacted in Europe had not heard
of the technology. 

Among possible applications of the technology are authentication of
communications and code, data encryption, privacy control, and DRM
(digital rights management), according to the report. 

While most talk of DRM revolves around music, Microsoft Chairman and
Chief Software Architect Bill Gates sees it as more useful for
controlling e-mail: Palladium could be used to limit forwarding of
messages or to make them unreadable after a certain time interval has
elapsed, the report said. 

Microsoft, for one, would benefit from being able to control e-mail in
such a way.  It has repeatedly fought to keep damaging internal e-mail
out of court records in recent cases, including its battle with the nine
non-settling states over remedies in its antitrust fight with the
Department of Justice. 

The technology needs to be widespread in order to be useful: 100 million
devices will have to be shipped "before it really makes a difference,"
the report quotes Microsoft Vice President Will Poole as saying. 

Palladium grew out of a skunk-works project looking for ways to secure
information stored on machines running Windows and became an official
Microsoft project in October 2001, according to the report. 

The first versions of Palladium "will be shipping with bugs," the report
quotes one of the project's cofounders, Paul England, as saying. 

Microsoft's record on software security has been heavily criticized in
the past, and in January of this year the company announced a new
emphasis on trustworthy computing in an effort to clean up its image. 
This news was soon followed by word that its software developers would
stop writing new code while they audited their existing code for
security flaws. 

Microsoft has long maintained that keeping its source code under wraps
makes its software more secure than open-source software such as rival
operating system Linux, where anyone can inspect the source code and see
its flaws.  A recent report from a Microsoft-funded think tank, the
Alexis de Tocqueville Institution, claimed that government use of
open-source software represents a threat to national security. 

Proponents of open-source software say this openness makes it more
secure, as there is a greater chance that flaws will be fixed and that
users will be more aware of the necessity of upgrading to a fixed
version of the software. 

Advocates of more open software development may be winning the argument. 
According to the Newsweek report, Microsoft will publish the source code
to its Palladium system in an effort to be more transparent. 

Publishing source code openly is not the same as declaring it to be
"open source." According to the Open Software Initiative, open-source
software must be freely distributable by third parties, including as
part of derivative works, without restriction or payment. 

Peter Sayer

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Free $5 Love Reading
Risk Free!
http://us.click.yahoo.com/3PCXaC/PfREAA/Ey.GAA/kgFolB/TM
---------------------------------------------------------------------~->

------------------
http://all.net/ 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 



This archive was generated by hypermail 2.1.2 : 2003-08-24 02:46:33 PDT