"P" <thomaspz@_takeout_bigpond.com> wrote:
> "Roy Smith" <> wrote:
>> You might find this page useful:
>> http://www.addictivetips.com/windows...windows-vista/
>> Although it's for Vista, it should work for Win 7 as well.
> Thanks for the link. I have been reading the comments on that page and the
> method seems to have caused several people problems that they will have
> real trouble getting out of. I read somewhere else that if this sort of
> thing it not done right the computer may never boot again.
I *strongly* advise against using the procedure described in the web page,
not because it won't work, but because it will.
DEP provides protection against a popular attack mechanism used by malware
to take control of your system. The short description is that it allows the
system to define areas of memory that should never contain executable code;
should the CPU ever be told to fetch an instruction from such an area it
will refuse to do so and will throw an exception.
Malware can exploit the lack of this protection by passing invalid data to
privileged programs that don't properly validate inputs; this corrupts part
of memory, causing the CPU to execute instructions provided by the attacker.
(This is one type of "remote code execution" attack.)
DEP can be a pain when non-malware programs trip over it, but in today's
world of massive botnets that grow by taking over victims' systems (not to
mention victims where keyloggers are installed and bank userids and
passwords are stolen) DEP offers a last line of defense.
> Is Microsoft just being hard to get on with stopping widely used software
> from doing its thing, maybe part of a MS - Adobe feud? It is totally wrong
> that a customer of these companies should be caught in the middle.
Lots of software products, especially older ones, trip over DEP. I won't
say that Micro$oft is likely to be unhappy about Adobe having problems, but
I've not run across anything in DEP that even faintly suggests that it's
intended to cause problems for any legitimate vendor. Relatively recent
versions of InstallShield, for example, have problems: I found that out
while trying to install some drivers from Dell where the driver was fine,
but the installer blew up.
> Anyway, how risky is this procedure? It seemed to work for only one person
> who commented. More had trouble.
With malware creators becoming increasingly sophisticated (the "script
kiddies" are still there but they aren't the big problem now) and able to
evade signature-based protections (antivirus programs) I would be far more
worried about malware getting through if I don't have DEP running than I
would be about a program that's (supposedly) still being supported by its
vendor.
Summary: push back - hard - on both Adobe and Microtex to get the problem
fixed. And look in the Application event log for clues that might help you
figure out what's triggering a DEP exception.
QUESTION for the entire newsgroup readership: has anyone else encountered
problems with TWAIN drivers when used through Acrobat? When used through a
non-Adobe program?
Joe Morris