[wix-devs] #5658 - Burn problem with AV

Sean Hall r.sean.hall at gmail.com
Thu Dec 13 10:28:08 PST 2018

The whole thing - because one person said their bundle built with v3.9
worked fine, and another implying that the issues started when using v3.11.
It's possible the companies are allowing one hop (unelevated->elevated) but
not two (unelevated->clean room->elevated).

On Thu, Dec 13, 2018 at 12:20 PM Rob Mensching <rob at firegiant.com> wrote:

> The initial report in that issue is about the elevated Burn not about the
> clean room. What part of the issue would be helped by not doing clean room?
> -----Original Message-----
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean
> Hall via wix-devs
> Sent: Sunday, December 9, 2018 3:02 PM
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Cc: Sean Hall <r.sean.hall at gmail.com>
> Subject: [wix-devs] #5658 - Burn problem with AV
> For https://github.com/wixtoolset/issues/issues/5658, I'm not convinced
> that we are going to be able to find a foolproof workaround for these
> problematic AV's. Would it be acceptable to add a /disablecleanroom switch,
> disable clean room if running in a specially name folder, or something else
> like that instead? I would think that would be ok security-wise since if a
> malicious entity can run our bundle with that switch they already have code
> execution.
> Also, have we submitted the latest v3.11 to each of the vendors in the
> issue - Avast, AVG, PC Matic SuperShield?
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant
> http://www.firegiant.com/

More information about the wix-devs mailing list