Windows XP SP2 Could Break Some Applications

Denver_80203 writes "An article from InfoWorld states that the upcoming Windows XP Service Pack 2 could break some 'unsecure applications.' In a quote from Tony Goodhew, a product manager in Microsoft's developer group says 'It doesn't really matter how long it is going to take you to do the work; security is an important issue and developers need to start doing that work now.' Or: 'The great bulk of applications will not be affected by memory protection. The number one that leaps to mind is execution environments with just-in-time code generation. The .Net Framework is one.' Fortunately for us, they are offering a course to guide the unsecure masses."

Comments

Re:.NET framework

[NSash]

.net framework will no longer be an option when the next version of windows comes out.

Microsoft's giving up that quickly?

A good thing

[Anonymous Coward]

The fact of the matter is that developers, particularly C++ developers like to do a lot of unnecesary tricks with memory. They like to push pointers around, execute from the stack and all.

This breaks abstraction, and makes their code very much hardware dependent. I'm glad they will be punished for their sins.

MS says: You will be forced to accept "upgrades".

[Futurepower(R)]

The marketing department at Microsoft has found another was to convince people not to use any Windows OS: Customers will be forced to accept "upgrades" if they want bug fixes.

This is abuse of customer trust, and a management failure at Microsoft.

Re:Uh oh

[Guppy06]

So the service pack will corrupt the Windows install? It's nice to see Microsoft hasn't changed a bit...

No, You get a clue

[Tenareth]

UNIX had memory protection on x86 CPUs since MINIX. The OS sucked, now they used hardware to finally make up for their sick oversights.

Oh, I have a great idea... let's make an OS that lets you execute random segments of memory...