Re:Don't copy paste from a website to a terminal
by maratd on Thursday November 12, 2015 @03:43PM
(#10555972)
That's too much work. It would be easier to just tell them to curl | sh and put all your malicious stuff in the script. That way they won't actually see anything malicious on their screen.
[ Parent
| on HN ]
Re:Don't copy paste from a website to a terminal
by redthrowaway on Thursday November 12, 2015 @03:52PM
(#10556018)
That requires more stupidity on the target's part. I think most devs know not to `curl | sh` random scripts, but something as innocuous as `ps -ef | grep /some/longish/annoying/path/to/script` would seem both safe at first glance and long enough to want to avoid typing.
Re:Don't copy paste from a website to a terminal
by kbutler on Thursday November 12, 2015 @04:06PM
(#10556131)
Do you download binaries? Do you build or install projects you've downloaded?
Those have the same risk as curl|sh
Re:Don't copy paste from a website to a terminal
by redthrowaway on Thursday November 12, 2015 @04:52PM
(#10556404)
With both binaries and curl|sh, trust in the source is a major factor in whether or not you do it. But copying an innocuous-looking terminal command (like `ps | grep`) doesn't seem like it would require trust.
I'll absolutely grab a binary or `curl | sh` from slack.com. I won't do it from a forum. But I would copy a terminal command that didn't look like it was doing anything fishy from a forum.
Re:Don't copy paste from a website to a terminal
by jacquesm on Thursday November 12, 2015 @05:00PM
(#10556450)
For a long time I had the bash fork bomb without any further explanation as my signature line on /, I'd just about forgotten about it when I got a really angry email from someone telling me that I'd blown up his server and thanks very much for that.