Re: VS2005/Vista issues

ACtually, it is reasonably important to me that under "normal" operating conditions that I
be unable to set hooks or send messages to elevated processes. Yet I still need to be
able to get privileges when I need them, but not be annoyed by having to type a password
each time. It sounds like these are incompatible goals.
joe
On Sat, 9 Jun 2007 11:51:46 -0700, "Alexander Grigoriev" <alegr@xxxxxxxxxxxxx> wrote:

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.

"David Ching" <dc@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%4qai.7287$u56.6575@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
news:reak63lhj9b6crv83kg4ve912hk1b4nras@xxxxxxxxxx
OK. But this will let me normally run with the lower privileges of an
ordinary user most
of the time, then?

Exactly. In Vista, there's no difference between an Admin user and a
Limited user, other than whether you need to provide an Admin password
when elevation is required or whether you just need to click Continue.


I'm still struggling with all this privilege stuff, but I want to be
testing in a "normal" user environment most of the time. So I really
want the extra
step---I've found that I don't need it *all* that often, so I'm trying to
create a
realistic test environment, but when I need it, I don't want to have to
give the password.
So I'll do as you suggest.

Yeah, this will work perfectly for you.

-- David



Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.