https://bugs.documentfoundation.org/show_bug.cgi?id=145490
--- Comment #15 from Mike Kaganski <[email protected]> --- (In reply to xordevoreaux from comment #13) > Doesn't explain why, ... Sure. To explain, one needs to invest much time in this brainless project of analyzing a paid closed-source antivirus for the patterns it catches, by trying to modify the binary in different ways, and see what triggers the detection, then analyze the compilation flags used on a specific build bot, its compiler version, its libraries, and finally see that the next version of this antivirus changed its detection, but finds something in another pattern, or another antivirus does equally confusing things. You report something detected by an antivirus. This is a valid report; thanks. It turns out to be a false positive (the file on server is the same that was initially generated, and the binary in it is indeed flagged e.g. testing on virustotal). The case is closed at this stage (because, again, for such cases the question is if the file was actually infected or not, and it was not). Your options are either trust this analysis (and maybe file something to the antivirus vendor, so that they have a chance to improve their detection), or not - and then it's your decision what to do next; it's *not* something to do in LibreOffice project. -- You are receiving this mail because: You are the assignee for the bug.
