Why is, it seems, that mingw is flagged
category: code [glöplog]
All my mingw compiled programs get the following message when downloading with chrome 33 on windows
Why is this? Even wth a program that looks like this
I still get that dirty message. Is there anything that can be done to prevent it?
Why is this? Even wth a program that looks like this
Code:
int main(void){ }
I still get that dirty message. Is there anything that can be done to prevent it?
In general any executable is considerred dangerous because a program can't analize another program to determine what it does so basically any executable and infact contain a hundreds of viruses. Even the programs that seem to have a purpose, something like a music player can in background install as many viruses it wishes.
Viruses spread like wildfire because people download and doubleclick on files like "top_10_cutest_kittens.jpg.exe"
Solution
1 - send only the source, never executables
2 - rename your files so that the extesion is not recognized eg .zip -> .z_i_p
This system is designed for protecting your standard everyday user who browses web and the most complicated thing this user can do on a computer is create a power point presentation.
Viruses spread like wildfire because people download and doubleclick on files like "top_10_cutest_kittens.jpg.exe"
Solution
1 - send only the source, never executables
2 - rename your files so that the extesion is not recognized eg .zip -> .z_i_p
This system is designed for protecting your standard everyday user who browses web and the most complicated thing this user can do on a computer is create a power point presentation.
Chrome complains about everything. No way around it, just ignore it.
I'd like not to ignore it. It's kinda embarrassing when someone tries to download one of my programs.
Does this happen with Visual Studio programs? I'm just wondering if it's specific
to mingw, so maybe then I could fix it
Does this happen with Visual Studio programs? I'm just wondering if it's specific
to mingw, so maybe then I could fix it
It gets a lot more lenient if the executable is digitally signed.
ooooohhhh!!!!! Ok cool. I'll look into that
Quote:
analize
What now?
use firefox.
Quote:
It gets a lot more lenient if the executable is digitally signed.
Exactly.. Newer versions of IE (10+ IIRC) will also complain.
Quote:
Does this happen with Visual Studio programs? I'm just wondering if it's specific
to mingw, so maybe then I could fix it
There is no guarantee, but in my experience binaries produced with alink (or similar free tools) are more likely to be reported as "dangerous", "trojan" or whatever by braindead security pretending borgware than those generated by MS tools.
Using a runtime compressor seems to be the #1 cause for false positives, though.
Solution: Avoid stupid semi-security solutions. And tell visitors of the website that the majority of todays widespread security add-ons are seriously flawed.
Quote:
Using a runtime compressor seems to be the #1 cause for false positives, though.
100% of my intros/demos are detected as virus because the exe are packed with kkrunchy :)
You know the solution to that.
Code your own exe packer as a replacement for kkrunchy :). Maybe make it a private group tool?
Code your own exe packer as a replacement for kkrunchy :). Maybe make it a private group tool?
This is just my solution - put a txt file in your ftp folder called something like "False AV Positives.txt" describing the use of packers and chrome's security settings. Also place a link to a good online av scanner - I always use jotti but you go with what you know. Maybe even place a regularly appended log file from said site in the same ftp folder.
lol. and i thought when norton internet security complained about mingw compiled stuff it was silly already...
