3 ms·
Arguably an insistence on stitching together systems out of 'do one thing and one thing only' minimalist components is precisely why Shellshock is so bad, thoug
by jameshart 12y ago
Arguably an insistence on stitching together systems out of 'do one thing and one thing only' minimalist components is precisely why Shellshock is so bad, though.
That so many things delegate setting environment variables to the system shell is what allows a vulnerability like this to be so pervasive. Why does a DHCP client pass server-originated data to a full shell? In some ways, it's a form of minimalism.
- SixSigma 12y agoIn band signalling = bad
- Florin_Andrei 12y agoNo, it's a form of laziness.
- clarry 12y ago> That so many things delegate setting environment variables to the system shell I think you've completely misunderstood the problem. The environment variable isn't and doesn't need to be set by a shell for shellshock to happen. Why shouldn't a DHCP client pass server-originated data to a shell? Or any other program? There is nothing wrong with passing data. The only problem here is that a specific shell had a bug.