No, nothing different from WiX v3.6. This morning I've gone ahead and
submitted the Burn engine to Symantec, Trend Micro and Kaspersky in hopes
that they will become familiar with Burn and figure out how to understand
that it is not a virus.
I'm thinking the best course of action would be to have
Rob,
I wasn't in any way implying that WiX was doing anything wrong - I agree
that it is Trend that are causing this. All i meant was i didnt know if 3.7
would be doing something sublty different that wouldnt trigger the 'malware'
alert.
Thanks.
--
View this message in context:
http://wind
I'm not sure whether submitting our product to Trend would have any effect,
since it is /behaviour/ that is triggering the alert, not any 'patterns' in
the setup code itself (if that makes sense)?
I can try this though. Presumably it is the extracted burn setup.exe that
needs to be sent, since th
I've never had to deal with that specific vender, but all of the ones I have
interacted with have had a means of submitting false positives. If you submit
your bundle to them, it usually takes less than a week for them to fix their
problem.
On Feb 26, 2013, at 8:57 AM, "Rob Mensching" wrote:
What should we do differently? We need a working folder to put all kinds of
stuff while we work on getting them in the right shape and/or verified
before putting them in their final resting place. The working folder needs
to be an unelevated location. The %TEMP% drive is used such that if
anything
We had (and still have) issues with 3.6 & Trend Officescan. It objects to
the way that the burn setup.exe is extracted into temp & then writes to the
RunOnce registry key. OfficeScan sees this as malware behaviour & blocks
it. Even though everything is signed.
If you havent signed everything th
6 matches
Mail list logo
