Crypto Trojan "Locky"

    • OMV 2.x
    • Crypto Trojan "Locky"

      What could in future be done from the side of the file systems used by OMV
      to prevent crypto-trojan "Locky" from encrypting all data on OMV shares?

      1) Automatically make all backed up files read only? Will this be enough?
      Or
      2) Automatically make all backed up files deletable only through a special password protected account?
      Or
      Add special characters to the file names on the OMV share so that a Windows client can not handle these?
      And make the special characters removable only through a password protected account?

      What do the file system experts here think should be done?

      Yours - Backupmaster
    • From what I can see, if you want to have Windows client accessing and writing Samba shares on OMV, there is very little you can do to stop the virus. Not using Samba, or read-only, is very inconvenient.

      The only real solution to an infection is backups (that are not also shared out r/w via Samba!). How to best achieve that depends on a variety of factors. For convenience, btrfs or ZFS snapshots would work very well.
    • rsnapshot the files to a non-shared drive works as well. This can be done very easily via the openmediavault-rsnapshot plugin.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!