Bug 20410 - Avast thinkgs output is a trojan hourse
Summary: Avast thinkgs output is a trojan hourse
Status: RESOLVED INVALID
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 7.2.3
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-06-05 23:33 UTC by Ian
Modified: 2014-06-06 18:39 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Avast (80.22 KB, image/png)
2014-06-05 23:33 UTC, Ian
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description Ian 2014-06-05 23:33:41 UTC
Created attachment 6998 [details]
Avast

Not sure how to fix this one...

See screenshot
Comment 1 Mikayla Hutchinson [MSFT] 2014-06-06 01:38:51 UTC
You should contact Avast, it's their heuristics.

Does it just happen with that app or all Xamarin.iOS apps?
Comment 2 Sebastien Pouliot 2014-06-06 18:39:21 UTC
Ian, Sadly there's nothing we can do on our end.

The best thing you can do is (like Michael said) contact Avast and provide them with the binary and a description of the problem, like:

"Somehow your software see a pattern inside an ARM executable, which is not something the Mac itself can execute. I'm not sure why it's even being scanned ?"