this post was submitted on 16 Sep 2023
81 points (84.0% liked)

Selfhosted

40113 readers
803 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

TL;DR - What are you running as a means of “antivirus” on Linux servers?

I have a few small Debian 12 servers running my services and would like to enhance my security posture. Some services are exposed to the internet and I’ve done quite a few things to protect the services and the hosts. When it comes to “antivirus”, I was looking at ClamAV as it seemed to be the most recommended. However, when I read the documentation, it stated that the recommended RAM was at least 2-4 gigs. Some of my servers have more power than other but some do not meet this requirement. The lower powered hosts are rpi3s and some Lenovo tinys.

When I searched for alternatives, I came across rkhunter and chrootkit, but they seem to no longer be maintained as their latest release was several years ago.

If possible, I’d like to run the same software across all my servers for simplicity and uniformity.

If you have a similar setup, what are you running? Any other recommendations?

P.S. if you are of the mindset that Linux doesn’t need this kind of protection then fine, that’s your belief, not mine. So please just skip this post.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] -1 points 1 year ago (4 children)

I am not a expert in Linux, and I mostly rely on very strong passwords. I also discovered recently basic stuff like changing the default SSH port. Anyone knows of implementation of 2FA on Linux?

[–] [email protected] 3 points 1 year ago (1 children)

I have a yubikey and use their pam-module for 2FA on sudo and ssh. Took a bit of time to configure, but now it works like charm: https://wiki.archlinux.org/title/YubiKey#Linux_user_authentication_with_PAM

[–] [email protected] 0 points 1 year ago

Thanks, I'm looking into it

[–] [email protected] 2 points 1 year ago (1 children)

Changing the default porta is security through obscurity, which is not security but just a waste of time. Don't rely on attackers "maybe not finding stuff" but rely on your stuff being secure, even if someone had all information about your network and system architecture.

For 2fa, the other commenter mentioned yubikey pam modules. Those are probably useful, but if you want to secure your ssh server, the best solution is to use ssh keys and disable password login. I can really recommend that as its one of the few things in security that improves both usability and security.

[–] [email protected] 1 points 1 year ago (1 children)

What's an ssh key? Nvm I'll research

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Welcome to the top of cryptography. We have elliptic curves, crazy math and huge numbers.

[–] [email protected] 1 points 1 year ago (1 children)

If at all possible, do not expose things like ssh, RDP, etc to the internet. Use traditional VPN or something like tail scale. Just because ssh is on a different port than normal doesnt mean an attacker couldn't figure out that your running ssh on port 335.

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago)

Well fail2ban went from very active to very quiet. It is definitely worth not leaving 22 (when opening ssh is a must for different reasons)