I set up a quick demonstration to show risks of curl|bash and how a bad-actor could potentially hide a malicious script that appears safe.

It’s nothing new or groundbreaking, but I figure it never hurts to have another reminder.

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

    This helped a lot. I had no clue I could post the curl string in the URL bar of a browser to view the script. Thanks for the education!

    • smeenz@lemmy.nz
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      2 days ago

      You had no idea you could paste a url into a browser’s location bar ?

      • aeiou_ckr@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        20 hours ago

        I wasn’t looking to get roasted for not knowing something. Guess that teaches me something else. Fuck people and thanking them for Shar something I didn’t know.

        • smeenz@lemmy.nz
          link
          fedilink
          English
          arrow-up
          1
          ·
          17 hours ago

          I think the general response is from confusion over what you could possibly have been using the url bar for in your browser if you didn’t know you could put urls there.

    • Nibodhika@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      2
      ·
      2 days ago

      You didn’t knew that the tool to handle URLs written in C (very creatively named C-Url) was handling URLs? It’s also written in C if you didn’t knew.