The Active Network
ActiveWin Anonymous | Create a User | Reviews | News | Forums | Advertise | VBA in Excel | Users Online: 0  
 

neowin.net

Amazon.com

  *  

  SP2 Presents XP Security Dilemma
Time: 10:41 EST/15:41 GMT | News Source: Computer Weekly | Posted By: Joshua Baer

Users will have to balance their IT security requirements with potential Java and .net performance problems if they are to take advantage of the features being introduced in Windows XP Service Pack 2. The highest level of security offered through SP2 will require the use of "no execution" (NX) technology, which is currently only available on machines equipped with AMD's Athlon an Opteron 64-bit chips. Gartner research fellow Martin Reynolds said, "Buffer overflow will be a lot harder to exploit under SP2." But he pointed out that some applications might not be compatible with NX. "Some code may deliberately execute from the data area - for example, just-in-time compilers for Java - and require the NX feature to be disabled," he said. Intel said its next Pentium 4 chip, Prescott, would not support NX.

Read Only Comments
Return to News
  Displaying Comments 1 through 3 of 3
  This is an archived static copy of ActiveWin.com.
#1 By 2332 (216.41.45.78) at Thursday, January 29, 2004 11:29:28 AM
I don't think this is entirely accurate, at least as far as .NET goes.

.NET does not execute code on the heap. All .NET code is compiled into machine code before it is run, and there for runs the same way "normal" code runs: on the stack.

In addition, I'm not entirely sure Java would be affected by this either. It's not like Java is calling methods on the heap simply because the byte code is loaded on to the heap. The byte code is translated into machine calls anyway, and those machine calls are executed on the JVM's stack. In addition, many performance critical Java applications use HotSpot technology anyway, which basically does what .NET's CLR does, and converts/caches byte code as machine code before execution.

Perhaps I'm misunderstanding something. Anybody?

#2 By 2459 (24.175.137.164) at Thursday, January 29, 2004 11:33:38 AM
Beat me to it, RMD. :-)

Some application behaviors are expected to be incompatible with execution protection. For example, applications that perform dynamic code generation (such as Just-In-Time code generation) that do not explicitly mark generated code with execute permission may have compatibility issues with execution protection. Note that managed code applications and components built on the Microsoft .NET Framework's common language runtime (CLR) will continue to work—the CLR is compatible with execution protection in SP2.

Application and driver developers should be aware of execution protection and the requirements of software running on a supporting platform. Applications that perform just-in-time (JIT) code generation or execute memory from the default process stack or heap should pay careful attention to execution protection requirements. The .NET Framework, for example, works with the NX bit set.


Windows XP Service Pack 2: A Developer's View
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwxp/html/securityinxpsp2.asp

#3 By 1845 (67.161.212.73) at Thursday, January 29, 2004 05:04:17 PM
The Itanium family supports NX.



 

  *  
  *   *
 
replica watches