Hmm, off the top of my head that sounds like you'll expose a security
vulnerability doing that. Unelevated data being passed to elevated process.
You'll also want to pass a hash or something to verify the file is the correct
file on the elevated (deferred) side.
-Original Message-
From:
property were it is safe.
-Blair
> From: chr...@iswix.com
> To: wix-users@lists.sourceforge.net; wix-users@lists.sourceforge.net
> Date: Tue, 26 Nov 2013 11:17:05 -0800
> Subject: Re: [WiX-users] DTF managed custom action - temporary file
>
>
>
> Here's another app
0
> From: phildgwil...@gmail.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] DTF managed custom action - temporary file
>
> If the users are different so is the temp location. The immediate CA gets
> the user's temp path, the system account (no impersonation
Here's another approach to consider:
http://blog.iswix.com/2011/10/beam-me-up-using-json-to-serialize.html
From: "Jens Teutenberg"
Sent: Tuesday, November 26, 2013 12:54 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] DTF managed custom a
If the users are different so is the temp location. The immediate CA gets
the user's temp path, the system account (no impersonation) uses the
system's temp path. As long as you create the file where both have access,
perhaps you could put the actual path to it in the registry.
Phil Wilson
On Tu
5 matches
Mail list logo
