Has anyone else hit with Avast recognising Optlink as a suspicious file since last update?

On Friday, 29 November 2013 at 03:58:59 UTC, Rikki Cattermole wrote:
> Has anyone else hit with Avast recognising Optlink as a suspicious file since last update?

The same issue.

I added dmd folder to trusted list.

On Friday, 29 November 2013 at 08:32:41 UTC, Pavel wrote:
> On Friday, 29 November 2013 at 03:58:59 UTC, Rikki Cattermole wrote:
>> Has anyone else hit with Avast recognising Optlink as a suspicious file since last update?
>
> The same issue.
>
> I added dmd folder to trusted list.

I'm going to report this to Avast as a false positive since you have confirmed it.
I won't send them Optlink because I'm not sure about license issues.

On Friday, 29 November 2013 at 10:50:53 UTC, Rikki Cattermole wrote:
> On Friday, 29 November 2013 at 08:32:41 UTC, Pavel wrote:
>> On Friday, 29 November 2013 at 03:58:59 UTC, Rikki Cattermole wrote:
>>> Has anyone else hit with Avast recognising Optlink as a suspicious file since last update?
>>
>> The same issue.
>>
>> I added dmd folder to trusted list.
>
> I'm going to report this to Avast as a false positive since you have confirmed it.
> I won't send them Optlink because I'm not sure about license issues.

Never mind I have to send it to them as by form.
Walter can you please confirm that I can do this?

On Friday, 29 November 2013 at 03:58:59 UTC, Rikki Cattermole wrote:
> Has anyone else hit with Avast recognising Optlink as a suspicious file since last update?

Since this spring I had issues when after linking my dmd-compiled program with libjpeg the result was reported to have something like
Gen:Trojan.Heur.GM.0444140020
by several different antiviruses, including BitDefender, Comodo and F-Secure but not including Avast.
What's interesting, when scanning the app without libjpeg linked in, it shows clean. When scanning libjpeg object file (which gets linked) it is clean too. But when the two are linked together antiviruses go mad.

Example of scan:
https://www.virustotal.com/en/file/808b46ee5cf568190b6075e39194b4442c0c3c36525d145ea546c2a3199265d8/analysis/1385745220/

Original file:
https://bitbucket.org/infognition/bsort/downloads/blogsort.exe

On Friday, 29 November 2013 at 17:20:17 UTC, thedeemon wrote:
> On Friday, 29 November 2013 at 03:58:59 UTC, Rikki Cattermole wrote:
>> Has anyone else hit with Avast recognising Optlink as a suspicious file since last update?
>
> Since this spring I had issues when after linking my dmd-compiled program with libjpeg the result was reported to have something like
> Gen:Trojan.Heur.GM.0444140020
> by several different antiviruses, including BitDefender, Comodo and F-Secure but not including Avast.
> What's interesting, when scanning the app without libjpeg linked in, it shows clean. When scanning libjpeg object file (which gets linked) it is clean too. But when the two are linked together antiviruses go mad.
>
> Example of scan:
> https://www.virustotal.com/en/file/808b46ee5cf568190b6075e39194b4442c0c3c36525d145ea546c2a3199265d8/analysis/1385745220/
>
> Original file:
> https://bitbucket.org/infognition/bsort/downloads/blogsort.exe

Avast reports no threat on that file you provided.

On Saturday, 30 November 2013 at 03:20:09 UTC, Rikki Cattermole wrote:

>> Example of scan:
>> https://www.virustotal.com/en/file/808b46ee5cf568190b6075e39194b4442c0c3c36525d145ea546c2a3199265d8/analysis/1385745220/
>>
>> Original file:
>> https://bitbucket.org/infognition/bsort/downloads/blogsort.exe
>
> Avast reports no threat on that file you provided.

Yes, virustotal confirms that. But says 10 other antiviruses do.

On Nov 29, 2013 4:00 AM, "Rikki Cattermole" <alphaglosined@gmail.com> wrote:
>
> Has anyone else hit with Avast recognising Optlink as a suspicious file
since last update?

Ahh, first world problems.  :)

Regards
-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';