Are you sure it was really a trojan? I use virus scanners, but the thing I don't like about them is all the false-positives. I always hear people claim they got a trojan or whatever, but you've got to remember that the virus scanner is not always correct. You know, heuristic (pattern matching) algorithms can be faulty. They are written by overzealous software developers who sometimes have a very poor understanding of heuristics. Their mentality is that NO code should perform certain operations.
I write and test a lot of machine code, written for various targets. Sometimes, I'll pull out of the old classics like TASM/MASM or A86 to test logic on an x86 platform, since debugging on a target can be difficult. Somehow my assembler will produce machine code that matches the signature of some virus, which is irritating. I know my code is clean because I check the CRC of the executable. Not to mention, I work on isolated machines with no network or external media access.
Also, for Windows developers, have you ever written code that calls SetWindowHookEx? Well, that's just one example of a call that might trigger a virus scanner on perfectly legitimate software.
Yeah, I grudgingly use antivirus software. . . but I'd rather not.
I write and test a lot of machine code, written for various targets. Sometimes, I'll pull out of the old classics like TASM/MASM or A86 to test logic on an x86 platform, since debugging on a target can be difficult. Somehow my assembler will produce machine code that matches the signature of some virus, which is irritating. I know my code is clean because I check the CRC of the executable. Not to mention, I work on isolated machines with no network or external media access.
Also, for Windows developers, have you ever written code that calls SetWindowHookEx? Well, that's just one example of a call that might trigger a virus scanner on perfectly legitimate software.
Yeah, I grudgingly use antivirus software. . . but I'd rather not.
