Posted Nov 24, 2010 8:58 UTC (Wed) by eru
Parent article: Ghosts of Unix past, part 4: High-maintenance designs
This did not apply at the time that setuid was first invented, but once Unix gained the #!/bin/interpreter (or "shebang") method of running scripts it became possible for scripts to run setuid.
As I remember it, running scripts as if they were executables predates #!. The new notation merely allowed the script to specify the interpreter. In older Unix versions, the system simply tried to feed into /bin/sh any file with x permission that it did not recognize as a binary executable.
to post comments)