I do not know of anyone locally that uses Norton's A.V. suite. I use
Comodo [like the dragon] for the free Internet Suite. I do not know how
hard it would be to remove a false-positive, but I have been using it
since I started using Vista. Now it gets installed on every system I
get my hands on that needs a "working" suite of security packages.
Now - can you work around a false-positive with Norton's? I know that
there is some with Comodo, more with the firewall than the a.v. but it
is there somewhere. I just do not use Windows much anymore to need it
for the a.v. part.
On 10/04/2013 09:20 AM, Tom Davies wrote:
Hi :)
Yet another advantage of OpenSource.
To get Norton to take notice it will probably take tens of thousands of people writing in to
grumble. So it would help if quite a few people on this list could grumble as that might be
enough to tip the balance whereas for just 1 person to write in sometimes feels like a complete
waste of time.
With OpenSource it only takes 1 person to grumble, and then a bit of luck to catch a dev's eye
when they aren't inspired to work on something else. Extra grumbles don't make much difference
and might even be counter-productive.
Regards from
Tom :)
________________________________
From: Joel Madero <jmadero.dev@gmail.com>
To: Tom Davies <tomdavies04@yahoo.co.uk>; Mister URL <terrance.bramblett@gmail.com>;
"users@global.libreoffice.org" <users@global.libreoffice.org>
Sent: Friday, 4 October 2013, 1:45
Subject: Re: [libreoffice-users] False Positive?
I would recommend emailing Norton and AVG and saying lower their
threshold. These false positives can come with stable releases as well
and they aren't our fault. These programs set these stupid system
thresholds to determine if something is malicious and then we get
blamed. There are several bug reports on FDO (our bug tracker) related
to this over the last few months and all have been closed as INVALID.
If enough people email Norton saying "hey we pay for this stuff and yet
we get these false positives" maybe they'll do something to make their
algorithm a bit smarter.
All the best,
Joel
On 10/02/2013 01:34 AM, Tom Davies wrote:
Hi :)
Not had a problem with it with AVG anti-virus.
Errr, you know that 4.1.2 is the most "bleeding edge" version in the "cutting edge" branch,
right? If you want stability and predictability then it's probably better to
a) wait until the 4.1.4 is fully released in a few months time or
b) go for the 4.0.5 instead
I go for option b.
Regards from
Tom :)
________________________________
From: Mister URL <terrance.bramblett@gmail.com>
To: users@global.libreoffice.org
Sent: Tuesday, 1 October 2013, 17:46
Subject: [libreoffice-users] False Positive?
I recently upgraded to LibreOffice 4.1.2. After installation, my Norton 360
advised that they had found and removed a bad thing, /Suspicious.Cloud.7.F/
from the installation folder of LibreOffice. I assume this is a false
positive. Has anyone else experienced this?
Thanks.
--
View this message in context: http://nabble.documentfoundation.org/False-Positive-tp4075891.html
Sent from the Users mailing list archive at Nabble.com.
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
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.