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.

  • non_burglar@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    2 days ago

    Have you ever looked at what was once ttek scripts? They’re a spaghetti of calls to other scripts. It’s not pretty. And not intuitive to audit.

    • burghler@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      2 days ago

      Wtf you’re my opposite D:

      I did and had a decent time with ctrl shift F’ing around. Took a moment since bash isn’t my strong suit.

    • interdimensionalmeme@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      4
      ·
      1 day ago

      They work so what is your objection ?
      If you are worried pipe it into chatgpt with the prompt
      “tell me why this script is safe to use”

      • non_burglar@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 day ago

        I thought I was being clear that I have audited some of the scripts. They are built referencing other scripts instead of functions, and these rely on URLs. It’s difficult to follow.

        Don’t ask chatgpt to audit code.