Would you be able to list some of the PUBLIC properties that would be propagated and not needed/wanted? It would be nice to know what may cause issues, and why. If the properties aren't used and don't affect the certain installers, then setting EnableUserControl=1 may work well for some developers.
Thank you, Jon On Wed, Jun 25, 2008 at 5:01 PM, Rob Mensching <[EMAIL PROTECTED]> wrote: > I always do the latter. There are a lot more PUBLIC Properties than you > might now and some of them could leak through data you don't need/want. > Basically, minimize attack surface. > > -----Original Message----- > Regarding the Vista installation issue of public properties not being > passed when the registry/domain settings are set to: > HKLM and HKCU Software\Policies\Microsoft\Windows\Installer > "AlwaysInstallElevated" (DWORD) to 1 > > Which of the following property settings is preferred? > > <!-- If the EnableUserControl property is set to 1, then the > installer can pass all public > properties to the server side during a managed installation > using elevated privileges.--> > <Property Id="EnableUserControl" Value="1" /> > > or, add public properties to SecureCustomProperties, by the Secure > option of each property such as: > > <Property Id="MYPROPERTYNAME" Secure="yes" /> > > Thanks, > Jon > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
