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.
i am glad its being shelfed for now
http://www.microsoft-watch.com/article2/0,1995,1585354,00.asp
Microsoft spent much of Day 2 of its Windows Hardware Engineering Conference (WinHEC) here refuting a published report claiming the company has axed its Next Generation Secure Computing Base (NGSCB) security technology.
“NGSCB is alive and kicking,” said Mario Juarez, a product manager in Microsoft’s security and technology business unit.
.. maybe not so soon, but it will come and all user-lemmings will love it. For a while …
Just my 2 Cent
I’m glad it’s gone for now, but DRM is real and it’s going to get more real. I’m hoping to make a total jump to linux by the end of next year
“Juarez said the project is being shelved because customers and ISV partners didn’t want to rewrite their applications using the NGSCB API set.”
“‘NGSCB is alive and kicking,'” said Mario Juarez, a product manager in Microsoft’s security and technology business unit.”
Maybe Juarez is just confused…
Microsoft never really axes software. If they make a big hubub about it and it gets a bad reaction, they say its canned. But, if you pay attention, you will see it is just separated and implemented in pieces or in separate products. So, it gets mostly/fully implemented without people raising a stink.
You never really win with Microsoft in this sense.
http://www.microsoft-watch.com/article2/0,1995,1585354,00.asp
But the recent qualifications made by the project team indicate that Microsoft still hasn’t solved key design issues for its version of the trusted PC security technology, which it calls the next-generation secure computing base, or NG-SCB. For example, the company’s software architects still haven’t decided on the way in which Microsoft will patch the core of the secure OS or allow for restoring backups to a computer. Both activities change protected data and will run afoul of the protections erected by NG-SCB.
This is the one thing about this technology that I haven’t been able to come to grips with either. Other than perhaps just auditing the hell out of its source to ensure that once released, it won’t require patches.
Any other ideas?
I love how the zealots leap for joy over something that hasn’t been cancelled.
Nice fact-checking there, crunchies.
http://www.wikipedia.org
informs of most important details and how it was/is planned to be used
Have a lot fun (reading)!
I always thought NX is the name of the compression library developed by NoMachine ( http://www.nomachine.com/ )….
Is it now happening that Microsoft is stealing this name from a small European company?
Today, I still find the info I’m looking for by typing “NX” into any search engine. But next month? Won’t Google hits be overpopulated by the new stuff the Redmond marketing machinery is streaming now?
i dunno why u posted this…
but nx in the contextg i know just is a flag of amd64 processors, a long time missed on x86 architecture…
this nx flag is for enable/disable executable memory…
yeah, some kind of hardware stack protection we want 🙂
has nothing to do with microsoft in this context.
but we all know there is a big chance tcpa will come and that tcpa is hard and software… and so ms of course will pugh its software to do its tcpa part. maybe they rename, rewrite and newspeak every second month… but we know the evil will come… and to guess ms cancelled paladium/ng…/tcpa is clearly untrue.
whether they rename it, or they just release fake infos to the press i dont care…
Eugene
”
Nice fact-checking there, crunchies.”
so you mean they are lying to the press and you are laughing at people who trust them. thats ironical
As one other poster pointed out Microsoft needs to rethink that name. They have been very busy filing lawsuits against Lindows and Mike Rowe. The same thing could be done back to them by a much smaller Italian company, NoMachine.
NX = NX
Change it Microsoft.
“perhaps the security system will be that only an administrator can install programs and a person needs to put in the admin password to do so!!!
and perhaps there will be a system admin who is the only person who has sufficient privileges to modify the system files and the files of other users!!!
GASP!!! that would be a true innovation brought to us by the 1970’s tech called UNIX!!!
oh please please please.”
Still doesn’t solve the problem of all those home users running as admin, they’ll just run as admin because it’s a pain to have to enter a password to simply install software. It would be great for the enterprise and most networked environments, but won’t change a thing with the home user.
NX is a technology on AMD’s Opteron processors(I don’t know about the Athlon64s though). It’s AMD who would be sued, not Microsoft.
And I don’t think they would be sued for something that trivial, anyway. It’s just a freakin’ acronym. It’s not like they were doing the promotion of it like Intel did with MMX and SSE.