Re: VS2005/Vista issues

Tech-Archive recommends: Fix windows errors by optimizing your registry

"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
news:g59d73luv7ul8a21lpqio7fsgnsr1j4rhq@xxxxxxxxxx
This question was based on the earlier reply in this thread:

Actually there is BIG difference. A "limited" process running under
administrator account can open a handle to an "elevated" process with full
access rights and screw with it any way it wants - run a remote thread,
inject code, etc. It's like being on the other side of the fence, but
still
having a key to the gate. So it's just an illusion of protection.

A process running under "true" limited user CANNOT open handle to an
administrator process. It even cannot send arbitrary windows messages to
it.

This suggests that if I make myself an administrator account (add my
account to the
administrator group) then I would NOT be subjected to the limitations of
my current
account. I want code that runs under my login account to have all the
llimitations of an
ordinary user (including to being able to set hooks, etc.), but if I run a
program that
wants privileges (as specified in its manifest) then it will prompt me,
and I can simply
click one mouse button to get them, so I can do the things I need to do
without massive
hassle while still getting a credible representation of what end users
will normally see.
joe


Yes, and I pointed out that the assertion you quoted is simply wrong, in my
experience. SetWindowsHookEx() does install a global hook, but you will see
your DLL does *not* get injected into elevated processes, if the injector is
not elevated.

-- David


.

Quantcast