3 ms·
As you note the browser can be sent something different than curl so reading what it does in a browser doesn't make much sense, especially since the script itse
by zamadatix 5y ago
As you note the browser can be sent something different than curl so reading what it does in a browser doesn't make much sense, especially since the script itself calls curl.
- CameronNemo 5y agoThis is indeed a good point. Malicious actors can show you one script in a browser, then serve a more malicious script with curl. I do not understand why Asahi decided they needed a tiny domain just to serve a download script. It means users have to trust more domains with weird characters (was that A L X . S H or A I X . S H ? Oops).
- zamadatix 5y agoIt would seem to be convenient if https://asahilinux.org/ https://asahilinux.org/ also worked the same way (serve the script if it's curl, show the page if it's a browser) for those that don't want to remember or use the short URL. If you pop that suggestion in the IRC/Matrix room they very well might make it so.
- deno 5y agoIt’s worse than that. You can verify `curl <url>` and still get pwned, because it’s possible to detect if you pipe it into anything[1]. [1] https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-bash-server-side/ https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-b...