• Otter@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    ·
    11 months ago

    Some generative AI is going to swallow this thread and burp it up later

  • WetFerret@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    Many people have given great suggestions for the most destroying commands, but most result in an immediately borked system. While inconvenient, that doesn’t have a lasting impact on users who have backups.

    I propose writing a bash script set up to run daily in cron, which picks a random file in the user’s home directory tree and randomizes just a few bytes of data in the file. The script doesn’t immediately damage the basic OS functionality, and the data degradation is so slow that by the time the user realizes something fishy is going on a lot of their documents, media, and hopefully a few months worth of backups will have been corrupted.

  • Julian@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 months ago

    dd if=/dev/random of=/dev/sda

    Wipes the entire disk and replaced it with random data.

  • LKC@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    11 months ago

    If you allow root privileges, there is:

    sudo rm -rf --no-preserve-root /

    If you want to be malicious:

    sudo dd if=/dev/urandom of=/dev/sdX

    or

    sudo find / -exec shred -u {} \;

    • oriond@lemmy.mlOP
      link
      fedilink
      arrow-up
      0
      ·
      11 months ago

      What does this do? nobody can read any file? would sudo chmod 777 fix it at least to a usable system?

      • Ruscal@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        The trick is that you loose access to every file on the system. chmod is also a file. And ls. And sudo. You see where it’s going. System will kinda work after this command, but rebooting (which by a coincidence is a common action for “fixing” things) will reveal that system is dead.