• cron@feddit.org
    link
    fedilink
    arrow-up
    78
    ·
    6 hours ago

    Well, malware devs should just ship as a docker container.

    version: '3.9'
    
    services:
      ransomware:
        image: totally-legit/malware:latest
        container_name: scary_encryption_bot
        restart: always
        volumes:
          - path_to_your_sensitive_files:/data
    
    • ThunderComplex@lemmy.today
      link
      fedilink
      arrow-up
      83
      ·
      5 hours ago

      Runs the docker container accidentally on my home server
      Home server is actually a RasPI
      This image is not available for arm64

      Sigh

  • varnia@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    74
    ·
    edit-2
    6 hours ago

    Customer: What is the attack vector of your virus?

    Virus Dev: People with profund GNU/Linux knowledge and OCD

  • quediuspayu@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    31
    ·
    6 hours ago

    Very relatable. Half the solutions I find online are for distros that do things slightly different that whatever I’m using.

  • anon5621@lemmy.ml
    link
    fedilink
    arrow-up
    14
    arrow-down
    1
    ·
    6 hours ago

    Cause it written in dumb way or for very specific systems normaly u could do static linking ,proper checks of fs and etc stuff and it will cover 90% of usual users