I have been away for the last two years. I restarted playing with GnuCOBOL and COBJAPI. Every time I compile a sample program, Norton pop ups checking the executable. Very annoying!!!
I wanted to get COBJAPI working again. I compiled the package just fine. I then compiled the example programs. When I run the examples, Norton complains that there is a virus deteched. The virus is IDP.Generic
I spent the afternoon looking through this forum and did not find anything. I then looked through the web and still no real answers. I hoping someone here might have some thoughts.
Norton seems to have made a lot of changes this year and not sure for the better.
Regards,
Rich Di Iulio
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As in other cases: it is good to double-check with virustotal.com - but this is Norton finding that something is strange with the gcc generated binaries, and indeed it is "strange" to compile binaries on Windows in the first place...
What I personally recommend is to create a clean folder where you verify what's getting in once and set it to the exception list of the AV/Internet-Security Suite.
The things that get in there first are stuff like MinGW/MSYS2, GnuCOBOL, ... and of course all COBOL binaries I create - doing so leads to a much faster compile and runtime and no nag screens that tell me "The OS you are running on is likely to get targetted - are you sure you can trust this specific binaries [from sources you've just compiled before]".
Note that in my experience Norton has the most false-positive "generic" (= looks strange) reports (which possibly is the correct approach if you want security and are not sure, but then needs a manual check and setup of exception folders).
Side note: If you can do this you may want to consider using WSL (so "GNU/Linux hypervirtualized on Windows") which would provide you with a faster compile and runtime (as long as you have a processor and bios/uefi enabled virtualization) and improved security. If you want to you still can run cobc/cobcrun residing there from Windows scripts by prefixing it with wsl.exe.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi All,
I have been away for the last two years. I restarted playing with GnuCOBOL and COBJAPI. Every time I compile a sample program, Norton pop ups checking the executable. Very annoying!!!
I wanted to get COBJAPI working again. I compiled the package just fine. I then compiled the example programs. When I run the examples, Norton complains that there is a virus deteched. The virus is IDP.Generic
I spent the afternoon looking through this forum and did not find anything. I then looked through the web and still no real answers. I hoping someone here might have some thoughts.
Norton seems to have made a lot of changes this year and not sure for the better.
Regards,
Rich Di Iulio
Hi Rich - and welcome back!
As in other cases: it is good to double-check with virustotal.com - but this is Norton finding that something is strange with the gcc generated binaries, and indeed it is "strange" to compile binaries on Windows in the first place...
What I personally recommend is to create a clean folder where you verify what's getting in once and set it to the exception list of the AV/Internet-Security Suite.
The things that get in there first are stuff like MinGW/MSYS2, GnuCOBOL, ... and of course all COBOL binaries I create - doing so leads to a much faster compile and runtime and no nag screens that tell me "The OS you are running on is likely to get targetted - are you sure you can trust this specific binaries [from sources you've just compiled before]".
Note that in my experience Norton has the most false-positive "generic" (= looks strange) reports (which possibly is the correct approach if you want security and are not sure, but then needs a manual check and setup of exception folders).
Side note: If you can do this you may want to consider using WSL (so "GNU/Linux hypervirtualized on Windows") which would provide you with a faster compile and runtime (as long as you have a processor and bios/uefi enabled virtualization) and improved security. If you want to you still can run cobc/cobcrun residing there from Windows scripts by prefixing it with
wsl.exe.