SyntaxBomb - Indie Coders

It actually happens a lot, generally more because of the type of tools they are, Blitz carrys a runtime with it, which MS Defender or other may pick up on if it's doing comparisons with stuff in it's definitions, UPX the executable compressor software gets hit a lot with it.

Sometimes these things get flagged as "potential" threats, not ACTUAL threats, and it'll throw itself an all singing and dancing wobbler about that, and remove the files without a simple "Are you sure you want to use this file?" question for the end user... The file... Flagged... Gone, well, unless you can deem it safe in security settings, that is, if the user knows how to do that.

All of it is sadly out of the developers hands, they can report it as safe, but then, it's all down to the company behind the security software to deem it so or not... Bit cack, but that's the way it is! :/

I reckon it wont be long before MS requires apps to be signed pretty much like Apple does, the freedom of developing and releasing is indeed slowly getting chipped away, maybe that is the point!?!

Dabz

Thanks @Dabz I have nothing to say, my apps being developed might have issue with users security and I only trust there are no actual virus, it would be good Microsoft can tell us that I am going to ask microsoft and play with security when I get to it. I don't think windows security had issue until I added networking with gnet iirc.

In my opinon, this is the correct approach for Anti-Malware (( albeit perhaps with some room for user override/control )) because unfortunaterly, some users simply do not have good sense or knowledge and allow all sorts of malware.

There's no real way to determine the trustworthiness of any software (beyond signed certificates, but these have been compromised in the past) and asking the author of malware if their product is safe to run is not likely to be of much value.

When you look at software like Blitz3D which inherently has lots of capacity to potentially create executables which can delete files etc. then it does indeed tick some, add to that the fact it was written in earlier times and certain standards/conventions have moved on for later OS requirements too and it's not really a huge surprise that it can be flagged as suspicious ---

BUT

suspicious isn't guilt and I think that security software needs to offer the user some form of authority to review any flagging events.