|
Sorry for the tardy response, there is not a way to obscure the value of a macro (macros are stored in a plaintext xml file, so this would only provide the appearance of protection). Not to mention that somewhere a macro setting would have be configured to obscure it's value (in the GUI), nothing would prevent any other user from changing this back and viewing the 'password' value directly.
To truly protect values in a build would require defining, maintaining and honoring individual user rights (obviously a limited number of users would need access to this value!)...
|