Setting up Exceptions with Least Risk - Signature vs Folders
Gepostet: 2022-03-14 | 13:48 · Bearbeitet: 2022-03-14 | 13:56 · 4 Antworten · Permanenter Link · Übersetzung:
[edit] clarify (why I did Signature vs Folder)
The Situation:
* I write code, and Anti-virus don't always love the code I write.
* Heuristic detection, "sometimes" thinks I just wrote a Virus or Virus like application.
The issue w/ writing code on a box is you cannot just add a File ID exception and remove from Quarantine and let that UI (Quarantine) make an Exception by Restoring the file. Why? Because you might re-compile 100 times in a day while testing, and each is unique, so each gets Quarantined w/o any folder or Signature exception.
From what I've been able to determine, setting up folder exceptions in "Items to Exclude from Auto-Protect, Script Control, SONAR and D.I.D." does not actually affect all the things that might scan for a Virus on a box w/ Norton Security. So I added a Signature exception, but that feels REALLY unsafe, compared to a little unsafe. I did this, because when I added an Exception for the folder that Microsoft Visual Studio (or other Code Studio) used as output, my files were still getting grabbed and it seemed to have no effect.
I noticed for Ms VS, it's a 2 folder solution, one for Objects & a 2nd for your bin once linked, still seemed to not work.
Followed this for Signature Exception, I had seen the listing in Settings, I wasn't sure how it worked at first:
* https://support.norton.com/sp/ko/kr/home/current/solutions/v115455517 (yes, it's in Korean, thanks Google)
Does anyone know if there's a better way for getting the things we write to be ignored at the time of Compile, w/o adding a Signature to an exception list?
This thread is closed from further comment. Please visit the forum to start a new thread.