I only discovered this recently, and it’s very handy.

Piping scripts directly to bash is a security risk. You can always download the scripts, inspect them and run locally if you so choose.

  • interdimensionalmeme@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    13 hours ago

    Read the scripts ? Why would anyone do that ? To truly understand even a relatively simply 10 page script can easily take an entire afternoon, this is a completely unrealistic demand.

    There is a piece of infrastructure missing, whether it’s no place to put ready to use LXC files, software installation script or configuration.nix files, there is a HUGE gap between the software that actually works, and the ability to go from nothing to a working computer.

    I have used my computer for my entire life, well over 30 years and even having spent my ENTIRE summer doing linux bullshittery, I still barely have anything working. Everything is delivered in a near broken mostly unusable state and that’s after you’ve spent multiple days to just get there.

    Almost nothing works and you simply don’t have enough time left in your life to even try making it work.

    So yes, people should pipe scripts into root shells without reading them because that’s what any real person would do. They really really should stop listening to all the nannies telling them to waste all their time re-inventing the wheel and achieving nothing.

      • interdimensionalmeme@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 hours ago

        I think it’s the rest of IT doing computers wrong, they’ve been very wrong for a very long time and getting wrong, unlockable bootloaders, motherboard-locked CPUs, it’s clear where all this “security” stuff is going, they’re building a prison one brick at a time.