Posted by: Fireberg
« on: 14. August 2010., 13:24:50 »So.....i still using mcAfee enterprise....
Thanx!!
Thanx!!
Members
Total Members: 14197- Latest: Levine
Stats
- Total Posts: 43445
- Total Topics: 16537
- Online today: 2794
- Online ever: 51419
- (01. January 2010., 10:27:49)
Users Online
Posted by: Fintech
« on: 13. August 2010., 09:43:50 »Truely odd from BitDefender, or isn't it really... all they (Virus safety programs) make mistakes sometimes! 
I won from here in the spring Panda Internet Security 2010, neither that be infallible!
That's true.
I won from here in the spring Panda Internet Security 2010, neither that be infallible!
That's true.
Posted by: Samker
« on: 12. August 2010., 07:23:18 »Very stupid "mistake"!
AVIRA
AVIRA
Posted by: Samker
« on: 12. August 2010., 07:21:43 »
German security firm Avira has admitted it falsely warned that a beta version of an upcoming security package from its Romanian rival was contaminated with a Trojan.
Few users outside the testing community would be running Avira and BitDefender 2011 beta 4 at the same time, so the incident is notable only as providing an illustration of how easy it is for security suites to trigger false positives.
News of the false alarm was broken on a Romanian language blog (here: http://devirusare.com/2010/08/08/epic-fail-avira-10-trdropper-gen-bitdefender-2011 ) and later confirmed by both firms involved.
"Avira mistakenly reported that the BitDefender 2011 product, that hasn't been publicly released yet, was a Trojan. We spotted this on August 10th and provided an automatic fix in the same day.” said Sorin Mustaca, manager of international software development at Avira.
Avira later explained, via a revised statement, that BitDefender's beta had "suspicious properties" that set off warning bells.
"Some components in the installer were modified so that the digital certificates became invalid. That's why it became suspicious. Installers "drop" components and start them; additionally the other suspicious properties were found so that a detection got triggered."
Vitor Souza, global communications director at BitDefender, said, “This is an issue with [Avira's] detection, and not a problem with BitDefender itself. Further, we should make you aware that this problem only affects the Beta 4 version of our product and not subsequent versions.”
(ElReg)