I have a scenario where I need to lock down a directory so that only system and a local service account that I'm creating can access it. I'm encapsulating this in a merge module.
I've tried two techniques: 1) Permission element nested under a CreateFolder element. The problem with this technique is the ConfigureUsers CA gets scheduled to execute before the base action of InstallFiles. This is *AFTER* the CreateFolders standard action. ?? This seems broken to me. 2) Util:PermissionEx element. This one doesn't have the forementioned problem but I haven't used it much in the past and I'm a little confused on how to break permission propogation and strip out the existing ACLs that are there. Any solution on making one of these or another work would be really appreciated. Thanks, Chris ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
