Microsoft decides against NGSCB in LongHorn (Updated)

With the increasing rate of viruses, software, music & video piracy and system break-ins over the past number of years, Microsoft aimed to tackle all these problems in its next operating system codenamed Longhorn.  They started work on its trusted computing project codenamed Palladium a few years back, but due to its controversial issues Microsoft then changed the name to NGSCB (Next-Generation Secure Computing Base).  Unlike previous Windows Upgrades, NGSCB would require new secure hardware to operate on as well as require applications to be rewritten to take advantage of its NGSCB API Set.

 

Now Microsoft has now decided to postpone its NGSCB as it would put too much pressure on trying to roll out secure chips as well as get software developers to rewrite their software in time for the LongHorn release, thus Microsoft went back to the drawing board.  They have now decided to use NX (No Execute) security technology which will also be supported in upcoming service packs for Windows XP and Server 2003 as well as the 64-bit editions of Windows XP and Server 2003.  While NX support will help prevent against buffer-overrun attacks in the newer AMD and Intel chips, it lacks all the secure DRM technology that NGSCB aims to offer.  Microsoft's decision will surely not please the recording and movie industries.  Thanks to jef195 for submitting the following news via our  news submit :

After a year of tackling the Windows security nightmare, Microsoft has killed its Next-Generation Secure Computing Base (NGSCB) project and later this year plans to detail a revised security plan for Longhorn, the next major version of Windows, company executives said.

On Tuesday, Microsoft executives confirmed that NGSCB will be canned. The project, dreamed up with Intel in 2002, was once code-named Palladium.

"We're evaluating how these NGSCB capabilities should be integrated into Longhorn, but we don't know exactly how it'll be manifested. A lot of decisions have yet to be made," said Mario Juarez, product manager in Microsoft's Security and Technology Business Unit. "We're going to come out later this year with a complete story."

Juarez said the project is being shelved because customers and ISV partners didn't want to rewrite their applications using the NGSCB API set.

Though Microsoft plans to use the NGSCB "compartmentalizing" technology in future versions of Windows, the company is moving swiftly to support No Execute (NX) security technology in newer AMD and Intel processors. NX reduces memory buffer overruns that many hackers exploit to insert malicious code into Windows and allows developers to mark pages as nonexecutable.

 

I am happy to see Microsoft's decision to at least postpone its NGSCB project.  While Microsoft may see this as a let down, it will definitely relieve the major controversial issue of upgrading to Longhorn.  While many novice users would see NGSCB as a useful feature, it would likely discourage many advanced users if they feel that the OS will be there to take control over the user. 

Feel free to discuss and read more about Windows and other operating systems on our General Software Forum.  More information on Microsoft's decision can also be found on The Register's news article.


(Update 7th May)


A few of our members have pointed out that a few
news sources including eWeek and Microsoft Watch have different news saying that Palladium is
Still Alive and Kicking.  According to this news
Microsoft aims to implement a portion of NGSCB v1 in LongHorn. 
This will enable the support of secure chips and TP enabled software when
they become available, but it means that existing hardware and software
will still be supported in LongHorn.  The next version NGSCB v2 will
require new secure hardware and compatible compatible software, however this
will not be the case for LongHorn.

Source: CRN - Daily News Archive

No posts to display