3 ms·
There are other methods of IPC other than shell variables. The shell is a known insecure environment, which is where there are limits on setuid for shell script
by nailer 12y ago
There are other methods of IPC other than shell variables. The shell is a known insecure environment, which is where there are limits on setuid for shell scripts.
By letting everyone on the Internet set shall variables Apache and whatever DHCPd (ISC?) did something they could have known would have bad consequences whether this feature/bug existed or not.
The only data Apache needs to control is Apaches.
- icebraining 12y agoFrom what I understand, Apache doesn't send them to bash. It sends the to whatever binary is configured to handle the request (using CGI), which were then calling bash unbeknown to Apache (but implicitly passing the same environment variables).
- ygra 12y agoLots of functions to start another process start a shell instead and is a command line to be executed, e.g. system or popen. The convenience in that case is that you don't need your own handling of $PATH or wildcards or argument parsing. It's pretty standard on UNIXoid systems.
- asveikau 12y ago> The convenience in that case is that you don't need your own handling of $PATH You don't with execvp or execlp either. > or wildcards or argument parsing. IMO this is of dubious value from, say, a C program. Why "parse" the args? Just generate a list...