Memory safe ‘curl’ for a more secure internet

Re:Memory safe ‘curl’ for a more secure internet by reificator on Friday October 09, 2020 @12:07PM (#24731271)

> This is no worse than if you were to have totally-not-evil.example.com give you the bash script on a floppy disk or something.

In practice, perhaps. But detecting whether the file is being piped to bash (and not cat/less/grep/etc) is pretty straightforward.

https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-b...

https://code.moparisthebest.com/moparisthebest/curl_bash

[ Parent | on HN ]

Re:Memory safe ‘curl’ for a more secure internet by staticassertion on Friday October 09, 2020 @01:31PM (#24732281)

Yeah, and it still doesn't matter. Because if you run that command you are already trusting that site with RCE on your machine, so if the premise of the attack is "the site is bad" you were owned anyways.

[ Parent | on HN ]

Re:Memory safe ‘curl’ for a more secure internet by dllthomas on Sunday October 11, 2020 @03:02AM (#24744212)

Moreover, the site could be legitimate and ship you something legitimate, but if it's truncated for any reason it could still be a "valid" bash script that now does incorrect things. Consider various prefixes of `rm -rf /tmp/thisscript.working/...`

[ Parent | on HN ]