Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


If it needs forensics to find out what was blocked, then the
av-solution is crap

        My thesis is that all av-solutions are deeply flawed =)

So only way is to do as already written in the buildinstructions and
common sense when actually looking at the AV-solutions' reports:
Disable monitoring for the build. Not only will that not break the
build, but also save some cycles for actually compiling stuff instead
of checking lots of intermediate files.

        I'd love to have some easy way of detecting any AV solution. I
suspect
doing something like this:

http://stackoverflow.com/questions/1331887/detect-antivirus-on-windows-using
-c-sharp

-
[nicholas ferguson] 
That is not a solution for 2014.  In the news you can read about groups of
people grabbing a ton of info from governments, companies...illegally
through some transport/internet protocols. 
So major companies have strict rules that even a developer cannot touch
their anti-virus settings.  Or if they try... they get dismissed.
So your solution  prevents that type of developer from working with
LibreOffice.



Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.