Comment on Privacy friendly Ubuntu antivirus ?

GnomeComedy@beehaw.org ⁨11⁩ ⁨months⁩ ago

• whale@lemm.ee ⁨11⁩ ⁨months⁩ ago

  [deleted]

  source

  • GnomeComedy@beehaw.org ⁨11⁩ ⁨months⁩ ago

    Everyone’s security profike/needs are different. The point is that list does a hell of a lot more useful than ClamAV

    source

    • whale@lemm.ee ⁨11⁩ ⁨months⁩ ago

      True, but like you said, on a per user basis. The typical desktop user isn’t going to have a clue about a text-based interface, unless they vaguely remember DOS or a room sized computer back in college that used the same terminal conventions that Linux still uses today

      source

      • GnomeComedy@beehaw.org ⁨11⁩ ⁨months⁩ ago

        Sounds like you’ve got a better solution, but I think you forgot to mention what it was.

        source

        • -> View More Comments
• neosheo@discuss.tchncs.de ⁨11⁩ ⁨months⁩ ago

  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?

  source

  • GnomeComedy@beehaw.org ⁨11⁩ ⁨months⁩ ago

    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 entire system on you.

    source

    • neosheo@discuss.tchncs.de ⁨11⁩ ⁨months⁩ ago

      How would you determine the configs that were modified? What do you mean put down?

      source

      • GnomeComedy@beehaw.org ⁨11⁩ ⁨months⁩ ago

        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)

        docs.ansible.com/ansible/latest/…/index.html

        source