Quote:
Originally Posted by sclitheroe
Just stick with Clam. Configure it to only demand-scan your downloads folder, and there will be no overhead from the resident engine trying to scan the rest of the system files as they are accessed on the disk. This gives you a little bit of security, and also keeps you compliant with their IT policy.
I'd go so far as to say, if you are working on documents collaboratively in your program (eg. project work) you have a bit of an obligation to your team to have antivirus - you want to break the chain of people passing around infected documents/pdfs, etc, even if they don't affect you. You also want to be able to share any content you find on the net safely, even if its not going to affect you either.
If you can get used to integrating a Mac into other organization's IT policy and frameworks, it will go a long way to your post-school employer letting you continue to use a Mac. Sticking out like a sore thumb with not antivirus, no password protected logins, etc, just pisses everyone off, and eventually you won't be allowed to use it.
|
Yeah I was thinking about this today. I didn't have any problems running Clam today. It passed the security check and I didn't even notice it was running.
I'll just stick with that. All the other points you just mentioned make a lot of sense, too. Thanks!