#9, One may have a tough time for a few weeks, explaining how substantive the changes in XP under SP2 actually are. For example, Remote Method Invocation [RMI] as manifest in DCOM, or a DCOM client like ActiveX are so deep that they are very difficult to explain. Controlling and making RMI safer was a central part of SP2 - one may run a simple test...start a download, for example, of the NW install package for SP2 itself, on one machine, but change the download location to a file or folder on another machine. Once completed, go to the target machine and right-click the downloaded file - you'll note a special button and some text next to it - the button says "Unlock" and advises that the file originated on another machine. The file cannot be opened and if an .exe, cannot be executed until it is unlocked - owing to the way RMI is now handled in XP - which of course, DCOM as at #1, above, would be covered by. Data Execution Protection [DEP] goes beyond the hardware cooperation with AMD and now Intel for newer chipsets and processors. DEP is by default present and protects XP SP2 systems files. This protection can be extended to any application as well and in case, does not require hardware support. DEP also goes beyond Buffer and Stack Over-Flow vulnerabilities, which may or may not be known or present. DEP extends protections to any memory used by the system and prevents malicious code from using this memory space. DEP is "on" by default on all XP SP2 systems, but is enhanced with hardware support. These protections may be extended to all programs - less those one specifically identifies. In the above simple example, one can see that Remote Methods cannot be Invoked without the LMZ operator's specifc knowledge and or permission. Hope this helps.
|