Emin.shopper Martinian.shopper wrote:
The source for subprocess just uses CreateProcess. Which means that,
short of monkey-patching it, you're going to have to roll your own
subprocess-like code (I think). Basically, you'll need to run
CreateProcessAsUser or CreateProcessAsLogonW. They're both a
> The source for subprocess just uses CreateProcess. Which means that,
> short of monkey-patching it, you're going to have to roll your own
> subprocess-like code (I think). Basically, you'll need to run
> CreateProcessAsUser or CreateProcessAsLogonW. They're both a bit
> of a pig in terms of getti
[slightly rearranged for top-to-bottom reading...]
On Mon, Jun 1, 2009 at 9:38 AM, Tim Golden wrote:
Emin.shopper Martinian.shopper wrote:
Dear Experts,
I am having some issues with the subprocess module and how it
interacts with win32security.ImpersonateLoggedOnUser. Specifically, I
use the
Thanks. But how do I fix this so that the subprocess does inherit the
impersonated stuff?
On Mon, Jun 1, 2009 at 9:38 AM, Tim Golden wrote:
> Emin.shopper Martinian.shopper wrote:
>>
>> Dear Experts,
>>
>> I am having some issues with the subprocess module and how it
>> interacts with win32securi
Emin.shopper Martinian.shopper wrote:
Dear Experts,
I am having some issues with the subprocess module and how it
interacts with win32security.ImpersonateLoggedOnUser. Specifically, I
use the latter to change users but the new user does not seem to be
properly inherited when I spawn further subp
Dear Experts,
I am having some issues with the subprocess module and how it
interacts with win32security.ImpersonateLoggedOnUser. Specifically, I
use the latter to change users but the new user does not seem to be
properly inherited when I spawn further subprocesses.
I am doing something like
