Am I missing something, or is this basically "copy this into your terminal" followed by "oh look, it did something"?
Ah yes, the legendary UN*X hacker who never pastes into his terminal.
*NIX
URL is also a shell script that executes some malicious(?) code
71–74 of 74 posts
Re: URL is also a shell script that executes some malicious(?) code
#72Earlier quoted context omitted.
(reply to sibling comment from unixbane which is [dead] for some reason:) > tell me the specific way you check your stuff before pasting so I can tell you how it's either broken or you're the 0.001% user and nobody else does that. I'm no 0.001% user, I'm not a shell expert and I can't catch everything but in the context of this particular post: - I know how string quoting in programming languages broadly works (no ne…
You can click the date of the post and then “vouch” if the post seems legitimate (I’ve done that for you now).
Thanks. I had done that but it doesn't fix ability to reply (at least not automatically - perhaps it summons mod intervention?)
Re: URL is also a shell script that executes some malicious(?) code
#73Earlier quoted context omitted.
If a carpenter chops his fingers off, it's not the fault of the saw. People who use programs should be expected to know what's safe to put in and out. Having a base level expectation of competence for operators is normal. A separate text input is just stdin by another name. Yes, I believe people who paste URLs into the terminal should examine those URLs - you generally have to trim some stuff, quote, or rewrite thing…
> If a carpenter chops his fingers off, it's not the fault of the saw. That would be an effective argument, but this vile shit has existed for decades without being fixed, for no good reason. This saw is specifically designed to slice fingers off, rather than do useful work, for no reason. > Having a base level expectation of competence for operators is normal. UNIX expects perfection, while providing none of its own…
Thanks for saving me a reply lol
Re: URL is also a shell script that executes some malicious(?) code
#74Earlier quoted context omitted.
How is it possible to be so wrong on so many levels in just two sentences? 1. Your epistemic reasoning capabilities are broken (as in, why do you think people should know better?) 2. You are just adopting an ad-hoc philosophy based on how shells work. If interactive languages had separate text inputs instead of just parsing a stream of text from stdin, pasting would always be safe. One may be tempted to call this "UN…
If a carpenter chops his fingers off, it's not the fault of the saw. People who use programs should be expected to know what's safe to put in and out. Having a base level expectation of competence for operators is normal. A separate text input is just stdin by another name. Yes, I believe people who paste URLs into the terminal should examine those URLs - you generally have to trim some stuff, quote, or rewrite thing…
> last paragraph
You can't safely paste anything into the shell ever lol. For multiple reasons. It doesn't matter how much visual inspection you do.