On 02-Feb-14 23:35, Sean wrote:
My problem with trying to make sure that variable values are
encrypted during runtime and zeroed out when freed is that I'm not
sure the encryption can be done in 3.x.
My assumption was that it would be transparent, decrypted when requested
from the BA or referenced in manifest authoring. Do you see a problem
where it wouldn't be?
So I guess what it comes down to is whether to have
SecureStringVariables even if the engine won't be encrypting what it
receives. The alternative would be creating yet another *Variables
(StringPointerVariables?) so that the managed BA doesn't have to use a
System.String.
My concern is that the presence of the property implies something that
won't be true until/unless it's backed by the engine.
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
