curl https://some-url | sh

I see this all over the place nowadays, even in communities that, I would think, should be security conscious. How is that safe? What’s stopping the downloaded script from wiping my home directory? If you use this, how can you feel comfortable?

I understand that we have the same problems with the installed application, even if it was downloaded and installed manually. But I feel the bar for making a mistake in a shell script is much lower than in whatever language the main application is written. Don’t we have something better than “sh” for this? Something with less power to do harm?

  • @[email protected]
    link
    fedilink
    English
    24 hours ago

    You could just read the script file first… Or YOLO trust it like you trust any file downloaded from a relatively safe source… At least you can read a script.

  • @[email protected]
    link
    fedilink
    107 hours ago

    For security reasons, I review every line of code before it’s executed on my machine.

    Before I die, I hope to take my ‘93 dell optiplex out of its box and finally see what this whole internet thing is about.

  • @[email protected]
    link
    fedilink
    10
    edit-2
    10 hours ago

    It isn’t more dangerous than running a binary downloaded from them by any other means. It isn’t more dangerous than downloaded installer programs common with Windows.

    TBH macOS has had the more secure idea of by default using sandboxes applications downloaded directly without any sort of installer. Linux is starting to head in that direction now with things like Flatpak.

  • @[email protected]
    link
    fedilink
    3621 hours ago

    What’s stopping the downloaded script from wiping my home directory?

    What’s stopping any Makefile, build script, or executable from running rm -rf ~? The correct answer is “nothing”. PPAs are similarly open, things are a little safer if you only use your distro’s default package sources, but it’s always possible that a program will want to be able to delete something in your home directory, so it always has permission.

    Containerized apps are the only way around this, where they get their own home directory.

    • @[email protected]
      link
      fedilink
      English
      4
      edit-2
      13 hours ago

      Don’t forget your package manager, running someone’s installer as root

      It’s roughly the same state as when windows vista rolled out UAC in 2007 and everything still required admin rights because that’s just how everything worked…but unlike Microsoft, Linux distros never did the thing of splitting off installs into admin vs unprivileged user installers.

      • @[email protected]
        link
        fedilink
        27 hours ago

        plenty of package managers have.

        flatpak doesn’t require any admin to install a new app

        nixos doesn’t run any code at all on your machine for just adding a package assuming it’s already been cached. if it hasn’t been cached it’s run in a sandbox. the cases other package managers use post install configuration scripts for are a different mechanism which possibly has root access depending on what it is.

    • @[email protected]
      link
      fedilink
      18 hours ago

      Docker doesn’t do this anymore. Their install script got moved to “only do this for testing”.

      Use a convenience script. Only recommended for testing and development environments.

      Now, their install page recommends packages/repos first, and then a manual install of the binaries second.

  • @[email protected]
    link
    fedilink
    922 hours ago

    Back up your data folks. You’re probably more likely to accidentally rm -rf yourself than download a script that will do it.

    • @[email protected]
      link
      fedilink
      English
      1
      edit-2
      13 hours ago

      To be fair that’s because Linux funnels you to the safeguard-free terminal where it’s much harder to visualize what’s going on and fewer checks to make sure you’re doing what you mean to be doing. I know it’s been a trend for a long time where software devs think they are immune from mistakes but…they aren’t. And nor is anyone else.

  • @[email protected]
    link
    fedilink
    English
    14
    edit-2
    1 day ago

    The security concerns are often overblown. The bigger problem for me is I don’t know what kind of mess it’s going to make or whether I can undo it. If it’s a .deb or even a tarball to extract in /usr/local then I know how to uninstall.

    I will still use them sometimes but for things I know and understand - e.g. rustup will put things in ~/.rustup and update the PATH in my shell profile and because I know that’s what it does I’m happy to use the automation on a new system.

      • @[email protected]
        link
        fedilink
        English
        10
        edit-2
        22 hours ago

        So tell me: if I download and run a bash script over https, or a .deb file over https and then install it, why is the former a “security nightmare” and the latter not?

        • @[email protected]
          link
          fedilink
          English
          212 hours ago

          Both are a security nightmare, if you’re not verifying the signature.

          You should verify the signature of all things you download before running it. Be it a bash script or a .deb file or a .AppImage or to-be-compiled sourcecode.

          Best thing is to just use your Repo’s package manager. Apt will not run anything that isn’t properly signed by a package team members release PGP key.

          • @[email protected]
            link
            fedilink
            English
            13 hours ago

            I have to assume that we’re in this situation because because the app does not exist in our distro’s repo (or homebrew or whatever else). So how do you go about this verification? You need a trusted public key, right? You wouldn’t happen to be downloading that from the same website that you’re worried might be sending you compromised scripts or binaries? You wouldn’t happen to be downloading the key from a public keyserver and assuming it belongs to the person whose name is on it?

            This is such a ridiculously high bar to avert a “security nightmare”. Regular users will be better off ignoring such esoteric suggestions and just looking for lots of stars on GitHub.

        • @[email protected]
          link
          fedilink
          English
          213 hours ago

          For example: A compromised host could detect whether you are downloading the script or piping it.

          • @[email protected]
            link
            fedilink
            16 hours ago

            Hilarious, but not a security issue. Just shitty Bash coding.

            And I agree it’s easier to make these mistakes in Bash, but I don’t think anyone here is really making the argument that curl | bash is bad because Bash is a shitty error-prone language (it is).

            Definitely the most valid point I’ve read in this thread though. I wish we had a viable alternative. Maybe the Linux community could work on that instead of moaning about it.

        • @[email protected]
          link
          fedilink
          English
          2
          edit-2
          12 hours ago

          You’re telling me that you dont verify the signatures of the binaries you download before running them too?!? God help you.

          I download my binaries with apt, which will refuse to install the binary if the signature doesn’t match.

          • @[email protected]
            link
            fedilink
            16 hours ago

            No because there’s very little point. Checking signatures only makes sense if the signatures are distributed in a more secure channel than the actual software. Basically the only time that happens is when software is distributed via untrusted mirror services.

            Most software I install via curl | bash is first-party hosted and signatures don’t add any security.

            • @[email protected]
              link
              fedilink
              English
              122 minutes ago

              All publishing infrastructure shouldn’t be trusted. Theres countless historical examples of this.

              Use crypto. It works.

        • @[email protected]
          link
          fedilink
          English
          1
          edit-2
          13 hours ago

          By definition nothing

          The point you appear to be making is “everything is insecure so nothing is” and the point others are making is “everything is insecure so everything is”

          • @[email protected]
            link
            fedilink
            16 hours ago

            No, the point I am making is there are no additional security implications from executing a Bash script that someone sends you over executing a binary that they send you. I don’t know how to make that clearer.

    • Possibly linux
      link
      fedilink
      English
      71 day ago

      Download it and then read it. Curl has a different user agent than web browsers.

      • billwashere
        link
        fedilink
        English
        41 day ago

        Yeah I guess if they were being especially nefarious they could supply two different scripts based on user-agent. But I meant what you said anyways… :) I download and then read through the script. I know this is a common thing and people are wary of doing it, but has anyone ever heard of there being something disreputable in one of this scripts? I personally haven’t yet.

        • Possibly linux
          link
          fedilink
          English
          21 day ago

          I’ve seen it many times. It usually takes the form of fake websites that are impersonating the real thing. It is easy to manipulate Google results. Also, there have been a few cases where a bad design and a typo result in data loss.

      • @lmmarsano
        link
        English
        122 hours ago

        I download it with curl. 🤷

  • @[email protected]
    link
    fedilink
    902 days ago

    You have the option of piping it into a file instead, inspecting that file for yourself and then running it, or running it in some sandboxed environment. Ultimately though, if you are downloading software over the internet you have to place a certain amount of trust in the person your downloading the software from. Even if you’re absolutely sure that the download script doesn’t wipe your home directory, you’re going to have to run the program at some point and it could just as easily wipe your home directory at that point instead.

      • @[email protected]
        link
        fedilink
        English
        27
        edit-2
        2 days ago

        You should try downloading the software from your mind brain, like us elite hackers do it. Just dump the binary from memory into a txt file and exe that shit, playa!

      • Ephera
        link
        fedilink
        English
        42 days ago

        It is kind of cool, when you’ve actually written your own software and use that. But realistically, I’m still getting the compiler from the internet…

    • @[email protected]OP
      link
      fedilink
      71 day ago

      Indeed, looking at the content of the script before running it is what I do if there is no alternative. But some of these scripts are awfully complex, and manually parsing the odd bash stuff is a pain, when all I want to know is : 1) what URL are you downloading stuff from? 2) where are you going to install the stuff?

      As for running the program, I would trust it more than a random deployment script. People usually place more emphasis on testing the former, not so much the latter.

  • @[email protected]
    link
    fedilink
    English
    51 day ago

    When I modded some subreddits I had an automod rule that would target curl-bash pipes in comments and posts, and remove them. I took a fair bit of heat over that, but I wasn’t backing down.

    I had a lot of respect for Tteck and had a couple discussions with him about that and why I was doing that. I saw that eventually he put a notice up that pretty much said what I did about understanding what a script does, and how the URL you use can be pointed to something else entirely long after the commandline is posted.