4 ms·
>curl -sL https://raw.githubusercontent.com/huan/docker-wechat/master/dochat.sh https://raw.githubusercontent.com/huan/docker-wechat/master/... | bash This is
by upofadown 7y ago
>curl -sL https://raw.githubusercontent.com/huan/docker-wechat/master/dochat.sh https://raw.githubusercontent.com/huan/docker-wechat/master/... | bash
This is a textbook example of something you should never ever do...
It gives some entity (usually a bunch or entities) you may not entirely trust an effortless way to own your system. You would need to download the script and carefully examine it to determine that it only does things you approve of. The fact that others might of downloaded from the same place makes no difference, every downloaded script could be different. Every script/binary the original script downloads could be different and malicious.
Just don't...
- Wowfunhappy 7y agoIs this different from running any other piece of software from the internet?
- dx87 7y agoThe only real difference is that there are ways the server can know if you are downloading it for inspection, or if you're piping it straight to bash. A hacked/untrusted site could serve up a malicious script file if it detects that it's being sent straight into bash, and a clean script if you aren't. With most things you download from the Internet, you download then run the software if you want. Curl to bash is download and run with no confirmation step in the middle.
- gruez 7y ago> Curl to bash is download and run with no confirmation step in the middle. Which is fine, because almost nobody is going to thoroughly inspect the code anyways. The bash script looks pretty trivial, but it's running a privileged docker container, which means it has full root access. Are you really going to inspect every nook and cranny of the docker container for exploits?