The developers of Microsoft reported an addendum to the Windows Vista SP1 new API (abb. of Application Programming Interface) for the implementation of NX technology, known as a Data Execution Protection.

Michael Howard (Michael Howard) writes: "In order to make our platform safer, we wanted to involve more people in the use of Data Execution Prevention (DEP or otherwise NX), so we decided to remove all barriers to development programs in Windows Vista SP1, Windows XP SP3 and Windows Server 2008. we added a few new API that will allow developers to customize the DEP to work with the process of their applications, rather than use the editor ties. new API also give developers a little more flexibility, if your application uses an older version of Abstract Type Library ( ATL). If you do not know what that is, it will tell you the story ATL.

ATL used very long as it is rather legkovesen and allows a developer to quickly create COM objects. It also includes classes for manipulating security descriptor. Frankly, ATL does work with Windows security objects dangerously open.

Older versions of ATL, I am referring to the Visual C + + 2005, using a dynamically created code in small isolated registers. It is clear that without the use of API will cause problems, as well as on the computers included with the DEP, you will not be able to perform certain types of data. This code will be forwarded as a transition (a small section of code performs the conversion or providing 32 call - bitne code of the 16 - bitne and vice versa - ca. Bottom). Rather ATL version, part of a set of VC + + 2005, works with the DEP.

The most important SetProcessDEPPolicy added to the API, which allows you to customize the DEP launched on the process. The function has only one argument: the policy settings. The options are:

The latter option - murderous argument: if you create a program that includes components that could be incompatible with the DEP, because they have been created using an older version of ATL, you can still use the DEP for your process. There are also two other features GetSystemDEPPolicy and GetProcessDEPPolicy.

The only negative point API data - they must be dynamically mapped because they are not supported in all versions of Windows. The following code illustrates how you can use these functions regardless of the version of Windows: