Microsoft to introduce hardware-linked security from XP-SP2

I just posted the article Microsoft to introduce hardware-linked security from XP-SP2.

  While we reported  that Microsoft will be introducing hardware-tied security called NGSCB in Longhorn,  Microsoft has now announced that it will introduce hardware-linked security in  Windows...
Read the full article here:  [](

Feel free to add your comments below. 

Please note that the reactions from the complete site will be synched below.

Well it looks like Windows XP SP1 might be the last OS I ever use :d

Guys this is serious stuff. If we don’t do something we are possibly going to get the rug pulled out from under us. This technology is to put a meter on the internet and all other content. Guess who is the meter maid? This story may be a bit over the top but it makes you wonder…
[edited by Crabbyappleton on 04.11.2003 03:24]

What a f@@ken joke.Hey bill why dont you try to write code that is worth a shit.Thats right you cant you have to steal it from everybody else!:d
[edited by electrician2002 on 04.11.2003 03:39]
[edited by electrician2002 on 04.11.2003 03:42]

They didn’t say if you could turn it off?! And JIT is used by .Net for all it’s executables… right?! You better be able to turn it off… also M$ could instead also be pushing the .Net framework application, with a fully managed environment, buffer overrun should be impossible.

Guys listen… They didn’t even mention the Intel 775 which is due out in 4 months so I dont think this is going to be a problem and if it is so what. As the article stated CSS was cracked so will this. Security is always one step behind Freedom.:X

.Net will work fine in this new security framework as all official .NET stuff is managed code, which is different than legacy JIT compilers.
[edited by Rhelic on 04.11.2003 15:00]

Get real , so far this sounds only as a mesure to prevent executing viruses and such. It MAY be used for DRM and reverse engeneering preventation but even if this will implemented it will be just another protection :slight_smile: However , I do hope MS will be smart enough to make a checkbox “allow this program to execute unprotected code” in prefferences to avoid problems with older software.

So instead of fixing the real problems with windows (again), they are going to do another half-assed fix. Woooo. I can’t wait to see how many apps break that aren’t supposed to :d

People will eat up DRM all Microsoft has to say is this will combat kiddy porn! And the fools will come running. We have to remove porn and free speech from the internet to save the children! Oh heck lets just burn all the books too, they might have some kiddy porn in them.
[edited by sorti on 05.11.2003 00:04]

Ok they have a monopoly on the hardware. They gave us no choice really and built this tecnology into both the intel and AMD chips. Which made me sick. The only thing to do, is to get together and spread by word of mouth not to support any software that uses this technology to take advantage of people. Switch to linux, or hell switch to macintosh. Don’t install software that uses the DRM fees to charge you, uninstall it, install something else. Support open source, learn how to program and make open source software. Just make it clear to microsoft that we don’t want our computers to take directions from them. We want our computers to listen to us.

I would think chip makers would give option to disable. after the bad press from intel using traking number in chips ect. Windows and chips using this tech will only be good for corp computing. Looks like MS has become like the old big blue of the 80s(IBM). Hopefully they will wake up before we all switch OS and use AMD/INtel clones…

U using Windows? U r crazy. Ditch it and go with Mandrake, Debian, Red Hat, etc. Windows :r - it gives me the SHIT!

BTW. Hardware DRM and BIOS DRM are very bad for consumers and may require mod chips or extra hardware to circumvent. Most likley we will just stop buying chips who design for MS and not consumers. Afterall who was AMD 10yrs ago? CSS was only cracked due to PC using SW not HW to decode and the key accidently exposed in SW code.

Chip and BIOS secruity can be turned off. and even if it’s on it doesn’t affect current software. The problem is if this technology goes mainstream then you’ll have to leave it on to run the majority of software and it may give software makers the ability to charge you per month for your software instead of a one time buy if a DRM system is built around the new features of this chip. Take note that microsoft has a patent on a DRM system that would take advantage of these features. So they’re planning to build one. If it goes mainstream the hardware makers may decide not to allow you to turn it off and your computer may become more locked down after time goes on. It’s like a frog. Put it in boiling water and it jumps out. Put it in cold water, and slowly warm the water up and it’ll boil to death. Just have to make sure there’s a plentiful amount of software out there that does not try and lock down your system. As for protected memory, and non-executable memory locations, well all PC X86 processors already had that functionality built in, since at least the 386 but MS never took advantage of it until Windows XP. Oh well.
[edited by chsbiking on 05.11.2003 13:39]

You are missing the big picture with hardware protections built in around the operating system. Companies will lap it up. Where companies adopt consumers have to follow it would seem in the current PC market.