I recently switched from Bitdefender to AVG, and like you just uninstalled AVG.
I'm not sure where to go from here.
I'm not sure where to go from here.
Are you using a recent version of Windows (8, 8.1, or 10)?
Do you have automatic updates enabled?
Do you have standard Windows features such as User Access Control enabled?
Do you use the computer with a standard user account as opposed to an administrator (root access) user account?
If the answers to all these questions are yes, I'd say you don't need an antivirus solution. Don't listen to the scaremongers. Microsoft has got you covered.
Run updates, don't use browser plugins, stick to applications you trust, and stay away from seedy looking sites when downloading common software. (Sourceforge comes to mind.)
For risky websites, a combination of Chrome, WOT, ublock origin, HTTPS Everywhere and Sandboxie and/or Malwarebytes Anti-Exploit (zero-day protection) should suffice.
Using a Standard (non-Admin) Windows account and being up to date goes without saying.
It's not that MS has you covered, moreso that AV vendors don't really catch new malware that has been mutated, packed, or whatever. So a more in-depth defense is better.
Not to mention that hilariously enough, AVG is literally selling user data now, which is what antivirus is supposed to protect against in the first place.
Linux.
I don't think it will be much longer until I actually make the switch.
if you don't, and you don't do webbrowsing from inside windows then I can't imagine the need for anti-virus.
90% of attacks are trojan horses (fake/embedded pirated software usually) and the remaining 9.9% is browser attacks.
I doubt anyone is defeating your firewall/NAT box to get a direct connection to your windows machine, and even if they did they'd have to find a service they can exploit.
:)
For some extra polish when running Linux VMs under VirtualBox on Windows, set the virtualisation mode to kvm and use virtio network device.
Security starts with the user.
How is this the same as having to run anti-virus software because the system's (i.e., Windows's) security model is broken?
> jailbreak iOS
Not sure why iOS is even relevant to my comment, since it isn't built on Linux (or even Unix).
> Security starts with the user.
This is true; a user who is bound and determined to hose their system can do it no matter what protections are in place.
But that's irrelevant to the point under discussion, which is how people who do not want to hose their system can keep it secure. On Windows, you have to run anti-virus software (and even the protection that provides is not foolproof), because the system's security model is broken. On Linux, the system's security model is functional to begin with, since unlike Windows, the system was designed that way from the ground up. So you don't need to run anti-virus software, and hence you don't have to worry about what information that software, which has a privileged position on your system, might be sending to others.
Yes, those things should be turned on by default. It is hard to educate generations used to work as root.
When people discuss UNIX security they tend to forget that worms were first targeted at them.
Also data matters more than system binaries, so it is enough to p0wn an application and suddenly $HOME is open to the world.
Then new GNU/Linux generations also seem very found of "curl ... | sh". Again opening $HOME to the world.
I also doubt everyone reads their emacs, vi, ..... packages. Again opening $HOME to the world.
UNIX does have a better security model configuration out of the box, but is just as unsafe for the regular users that just dump stuff into their PCs.
Do you still need to run anti-virus software in this configuration?
> UNIX does have a better security model configuration out of the box, but is just as unsafe for the regular users that just dump stuff into their PCs
Again, I agree, if a user wants to hose their system, Unix won't prevent them. But anti-virus software won't prevent them either.
My point is, what about the user that doesn't want to hose their system? On Linux, it's very simple: use your package manager to install software, and don't run anything that wasn't installed that way.
Just that trusted sources in Windows means not installing pirated software or that thing a friend gave because it was so cool. Or going to shady internet sites.
All things that will hose a Linux system as well.
Linux package managers are nice until one needs something it isn't there, like it happens to most average users that don't care about about FOSS and forcing themselves to alternatives.
And I never saw a UNIX that would allow to prevent users to install software locally, as Windows does with Active Directory group policies. Although I bet there are some third party commercial offerings for that.
Outside Windows I only saw that in mainframes.
What does "trusted sources" mean in the Windows world? Microsoft itself has shipped virus-infected CD-ROMs in the past.
> Linux package managers are nice until one needs something it isn't there
My sense is that, while this can happen, it's less likely to happen with the major Linux distros than it is with Windows. Major distros have tons of software in their package managers.
> I never saw a UNIX that would allow to prevent users to install software locally, as Windows does with Active Directory group policies
Um, you do realize that all it takes is not putting the user in the "sudoers" or "wheel" group (depending on the distro), right? This is routinely done in settings where only sysadmins are allowed to install software, such as universities. You certainly don't need anything as heavyweight as Active Directory group policies.
Do you also read OpenSSH and Bash source code looking for security exploits?
> My sense is that, while this can happen, it's less likely to happen with the major Linux distros than it is with Windows. Major distros have tons of software in their package managers.
Quantity != Software X that user won't do without.
> Um, you do realize that all it takes is not putting the user in the "sudoers" or "wheel" group (depending on the distro), right? This is routinely done in settings where only sysadmins are allowed to install software, such as universities. You certainly don't need anything as heavyweight as Active Directory group policies.
I can install whatever software I want under $HOME, there is nothing preventing me to do that.
I don't personally, no. But I'm confident that there are experts doing so, and that when they find an issue, it is publicized and fixed quickly, because it's considered an extraordinary and urgent event, and allowing it to continue unfixed would be unacceptable. When MS shipped virus-infected CD-ROMs, nobody thought it was unacceptable, or even abnormal.
However, if you're confident enough in Windows' security features to run without anti-virus software, that's fine. My sense is that the vast majority of Windows users are not. But the vast majority of Linux users are.
> Quantity != Software X that user won't do without.
You're going to have to give specific examples, because I just don't see this as a significant issue that users who don't want to hose their systems have to deal with on Linux. I've never come across any software I needed as an ordinary user that I couldn't find in my Linux distro's package manager. (As a programmer, I have, but that's a different case.)
> I can install whatever software I want under $HOME
Which comes under the heading of users who want to hose their systems. If you don't want to hose your system, just don't do that.
(As an aside, I think you can actually lock down executable permissions in $HOME with SELinux. But I haven't tried it myself.)
No where. I've been antivirus-free for the better part of a decade. 0 infections of malware of any kind.
Have a look at this link, it explains things a whole lot better than I could:
http://www.cnet.com/how-to/i-dont-use-anti-virus-software-am...
if you keep your OS and browser up to date, and don't open random sketchy EXEs, you'll be fine.
The old school Unix method works very well: Keep a list of all changes made from the base install, then periodically swap the disk out for a blank one, follow your documentation and restore non-executable user data from backup. Also has the benefit of regularly validating your documentation and testing your backups, and allows easy rollback by following the same process for major OS updates or hardware upgrades.