Again, seriously question why you need this but you could look into ClamAV. If you're coming from Windows you're going to be in for a shock if you blindly try and adapt every concept from Windows straight to Linux.
this post was submitted on 24 Oct 2023
14 points (100.0% liked)
Privacy Guides
16805 readers
28 users here now
In the digital age, protecting your personal information might seem like an impossible task. We’re here to help.
This is a community for sharing news about privacy, posting information about cool privacy tools and services, and getting advice about your privacy journey.
You can subscribe to this community from any Kbin or Lemmy instance:
Check out our website at privacyguides.org before asking your questions here. We've tried answering the common questions and recommendations there!
Want to get involved? The website is open-source on GitHub, and your help would be appreciated!
This community is the "official" Privacy Guides community on Lemmy, which can be verified here. Other "Privacy Guides" communities on other Lemmy servers are not moderated by this team or associated with the website.
Moderation Rules:
- We prefer posting about open-source software whenever possible.
- This is not the place for self-promotion if you are not listed on privacyguides.org. If you want to be listed, make a suggestion on our forum first.
- No soliciting engagement: Don't ask for upvotes, follows, etc.
- Surveys, Fundraising, and Petitions must be pre-approved by the mod team.
- Be civil, no violence, hate speech. Assume people here are posting in good faith.
- Don't repost topics which have already been covered here.
- News posts must be related to privacy and security, and your post title must match the article headline exactly. Do not editorialize titles, you can post your opinions in the post body or a comment.
- Memes/images/video posts that could be summarized as text explanations should not be posted. Infographics and conference talks from reputable sources are acceptable.
- No help vampires: This is not a tech support subreddit, don't abuse our community's willingness to help. Questions related to privacy, security or privacy/security related software and their configurations are acceptable.
- No misinformation: Extraordinary claims must be matched with evidence.
- Do not post about VPNs or cryptocurrencies which are not listed on privacyguides.org. See Rule 2 for info on adding new recommendations to the website.
- General guides or software lists are not permitted. Original sources and research about specific topics are allowed as long as they are high quality and factual. We are not providing a platform for poorly-vetted, out-of-date or conflicting recommendations.
Additional Resources:
- EFF: Surveillance Self-Defense
- Consumer Reports Security Planner
- Jonah Aragon (YouTube)
- r/Privacy
- Big Ass Data Broker Opt-Out List
founded 1 year ago
MODERATORS
It's not a bad thing to have an antivirus, especially now that we see more viruses made for Linux specifically. I still don't worry much myself, because the number isn't that huge, but if there was an easy to use antivirus GUI app I think I'd try it
Anyone is welcome to install an AV on their device if they so choose. I was more alluding to the fact that there are many things you should be doing to prevent malicious programs from running on your computer in the first place. By the time it makes it onto your system you're really just hoping that an AV would happen to catch it.
Yes, that's a good point, being careful goes a long way, though exploits can really come from anywhere.
Clam
AVs in Linux realm exist mostly for scanning windows stuff for email attachments, shared storage, etc.
I recommend this video from Rob Braxman titled Why an Antivirus Does Nothing for You, just came out recently: https://invidious.flokinet.to/watch?v=mE7CCZCgRB8
You're pretty save without an Antivirus on Linux (we're just 3%, not worth it for hackers), but if you need to check files, VirusTotal is your friend.
You'd be better served learning how to setup and use:
- backups (and test them)
- automate your reinstall (see ansible)
- firewalld (RHEL/Fedora) or ufw (Ubuntu)
- fail2ban
- SELinux (RHEL/Fedora) or AppArmor (Ubuntu)
- disable SSH via password, use keys only
- adblocker (like ublock origin) - credit to whale@lemm.ee for the idea below
For the automating of reinstalls what do you mean?
Is it just a playbook that installs the distro, them installs the same packages, and then restores things like /home from backup?
That, and:
- put down config files that were modified
- enable/start services that were installed
- modify the firewall to open necessary ports
Basically: put everything back as it was right before the ransomware encrypted your system on you.
Then of course - fix what you did wrong that got you compromised. ;-)
How would you determine the configs that were modified? What do you mean put down?
Ideally you keep your configs in a git repo (like github). You know what's modified because you're the one who modified them. If you modify them - put that config file in the git repo.
As for "put down" I just meant copied to the system (from github) by your automation (like ansible)
https://docs.ansible.com/ansible/latest/getting_started/index.html