Re:OpenBSD now enforcing no invalid NUL characters in shell ...
by lupusreal on Tuesday September 24, 2024 @09:39AM
(#41636342)
Does this break those self-extracting script/tar files? I forget how those are done, I haven't seen one in many years.
[ Parent
| on HN ]
Re:OpenBSD now enforcing no invalid NUL characters in shell ...
by jancsika on Tuesday September 24, 2024 @11:48AM
(#41637847)
If you don't know anything about OpenBSD, here's a fun thing:
1. Randomly choose "yes" or "no" to this question.
2. Read the post and get the answer.
3. Repeat until you begin to get a tingly "Spidey sense" that overrides your random-choice.
My Spidey sense here was, "Yes, because OpenBSD would have already thought about and covered that use-case." And indeed, toward the end of the post, that contingency is covered and documented.
Note: if you try this at your job and sense that the company will almost always choose the worst option, you should probably leave that job.
Re:OpenBSD now enforcing no invalid NUL characters in shell ...
by zx2c4 on Tuesday September 24, 2024 @09:43AM
(#41636378)
From the article: "It remains possible to put arbitrary bytes AFTER the parts of the shell script that get parsed & executed (like some Solaris patch files do). "
Re:OpenBSD now enforcing no invalid NUL characters in shell ...
by sneela on Tuesday September 24, 2024 @09:56AM
(#41636501)
Are you talking about Shar?
Re:OpenBSD now enforcing no invalid NUL characters in shell ...
by ape4 on Tuesday September 24, 2024 @10:10AM
(#41636631)
That was a neat idea back in the day but should disallowed now.
Running downloaded executables considered harmful.
Re:OpenBSD now enforcing no invalid NUL characters in shell ...
by osmsucks on Tuesday September 24, 2024 @11:14AM
(#41637411)
> Running downloaded executables considered harmful
Most executables are downloaded. :)
Re:OpenBSD now enforcing no invalid NUL characters in shell ...
by Joker_vD on Tuesday September 24, 2024 @10:29AM
(#41636826)
Not in the "Installation: just run `docker run kekw/our-shiny-ai-chatbot` in your shell" world we're living today.
Re:OpenBSD now enforcing no invalid NUL characters in shell ...
by nucleardog on Tuesday September 24, 2024 @10:39AM
(#41636962)
I think the better example is the all-too-common: “Installation: Just run `curl -sL http://goo.gl/hsjdiNgtehsn | sudo bash`”
Re:OpenBSD now enforcing no invalid NUL characters in shell ...
by 73kl4453dz on Tuesday September 24, 2024 @11:41AM
(#41637753)
They were generally uuencoded or similar