You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to make request to mark ExecXmlConfig, ExecXmlFile and ComPlusInstallExecute custom actions with Hidden Target flag as it is done for ConfigureIIs7Exec, for instance.
We have CA to encrypt configs, but we use XmlConfig to put passwords there. We also install COM+ application with provided user credentials.
There is a partial _workaround_ for Xml CAs: you have to explicitly define ExecXmlConfig and ExecXmlFile properties with Hidden attribute to hide their values in the property dump at the end of log; and create stab XmlConfig/XmlFile nodes before the one with sensitive data till the value of ExecXmlConfig and ExecXmlFile properties are truncated enough when CA is executed.
I didn't find any workarounds for ComPlusInstallExecute CA though.
I know this is a veeeery old issue, but hey! better late than never, right? Btw congrats with 3.10 release!
Originally opened by verba.vadim
The text was updated successfully, but these errors were encountered:
The workaround of marking the appropriate properties as hidden works today. The feature request is to create a set of parallel "secure" custom action entry points that hide everything by default.
Release changed from v3.10 to v3.x Type changed from Bug to Feature
Greetings, Gurus of Installer!
I'd like to make request to mark ExecXmlConfig, ExecXmlFile and ComPlusInstallExecute custom actions with Hidden Target flag as it is done for ConfigureIIs7Exec, for instance.
We have CA to encrypt configs, but we use XmlConfig to put passwords there. We also install COM+ application with provided user credentials.
There is a partial _workaround_ for Xml CAs: you have to explicitly define ExecXmlConfig and ExecXmlFile properties with Hidden attribute to hide their values in the property dump at the end of log; and create stab XmlConfig/XmlFile nodes before the one with sensitive data till the value of ExecXmlConfig and ExecXmlFile properties are truncated enough when CA is executed.
I didn't find any workarounds for ComPlusInstallExecute CA though.
I know this is a veeeery old issue, but hey! better late than never, right? Btw congrats with 3.10 release!
The text was updated successfully, but these errors were encountered: