For a long time, it is advised against to curl | sudo sh or equivalent:
- [WayBack] why using curl | sudo sh is not advised? – Stack Overflow
Because you are giving root access to whatever script you are executing. It can do a wide variety of nasty things.
- [WayBack] The Security Spectrum of curl | sh
By far the most irresponsible use of curl | sh is to use it with plain, unauthenticated, insecure HTTP instead of HTTPS. This is because it’s not only possible, but also increasingly likely, that the connection over which the shell script is delivered could have its contents silently modified by anyone in network position between the vendor and the installer—especially if you’re using public Wi-Fi. (If you don’t believe this is a real risk, consider that some companies’ business models revolve around modifying JavaScript delivered over HTTP in-transit—and anyone can hijack Wi-Fi with inexpensive, easy-to-obtain devices.)
So I’m surprised that companies still run content – include JavaScript – over an insecure http transport channel in their customers IDE instances.
Many developers run their IDE as Administrator, but even as regular user this is a large security risk: the transport layer is the easiest to hack and will eventually be hacked.
One such occasion was [WayBack] Delphi 10.2.3: Tools > Options Click OK = Script Error I have another weird situation with Delphi 10.2.3. Anytime I open up the options and click OK I … – Michael Riley – Google+ .
That one actually showed the script executed, but normally you do not see it happening at all.
So my advice:
Run the web-traffic from your development machines over a web-proxy like HTTP Fiddler, then disable all http based scripts.
–jeroen
Line 73: https://gist.github.com/jpluimers/40a60ca1e07bb91fa337ecfebe314d64#file-cf-common-js-L73
Read the rest of this entry »