Views
3 years ago

INTRO (7) NetBSD Miscellaneous Information Manual INTRO (7 ...

INTRO (7) NetBSD Miscellaneous Information Manual INTRO (7 ...

SCRIPT (7)

SCRIPT (7) NetBSD Miscellaneous Information Manual SCRIPT (7) Most shells (such as sh(1)) and certain other facilities (including execlp(3) and execvp(3) but not other types of exec(3) calls) still pass interpreter scripts that do not include the “#!” (and thus fail to execute with ENOEXEC) to /bin/sh. As this behavior is implemented outside the kernel, there is no mechanism that forces it to be respected by all programs that execute other programs. It is thus not completely reliable. It is therefore important to always include #!/bin/sh in front of Bourne shell scripts, and to treat the traditional behavior as obsolete. EXAMPLES Suppose that an executable binary exists in /bin/interp and that the file /tmp/script contains: #!/bin/interp -arg [...] and that /tmp/script is set mode 755. Executing $ /tmp/script one two three at the shell will result in /bin/interp being executed, receiving the following arguments in argv (numbered from 0): "/bin/interp", "-arg", "/tmp/script", "one", "two", "three" Portability Note: Multiple arguments The behavior of multiple arguments on the “#!” line is highly non-portable between different systems. In general, only one argument can be assumed to work consistently. Consider the following variation on the previous example. Suppose that an executable binary exists in /bin/interp and that the file /tmp/script contains: #!/bin/interp -x -y [...] and that /tmp/script is set mode 755. Executing $ /tmp/script one two three at the shell will result in /bin/interp being executed, receiving the following arguments in argv (numbered from 0): "/bin/interp", "-x -y", "/tmp/script", "one", "two", "three" Note that "-x -y" will be passed on NetBSD as a single argument. Although most POSIX style operating systems will pass only one argument, the behavior when multiple arguments are included is not consistent between platforms. Some, such as current releases of NetBSD, will concatenate multiple arguments into a single argument (as above), some will truncate them, and at least one will pass them as multiple arguments. The NetBSD behavior is common but not universal. Sun’s Solaris would present the above argument as "-x", dropping the " -y" entirely. Perhaps uniquely, recent versions of Apple’s OS X will actually pass multiple arguments properly, i.e.: NetBSD 3.0 May 6, 2005 2

SCRIPT (7) NetBSD Miscellaneous Information Manual SCRIPT (7) "/bin/interp", "-x", "-y", "/tmp/script", "one", "two", "three" The behavior of the system in the face of multiple arguments is thus not currently standardized, should not be relied on, and may be changed in future releases. In general, pass at most one argument, and do not rely on multiple arguments being concatenated. SEE ALSO awk(1), csh(1), ksh(1), sh(1), chmod(2), execve(2), intro(2), execlp(3), execvp(3), fd(4), options(4), setuid(7) STANDARDS The behavior of interpreter scripts is obliquely referred to, but never actually described in, 1003.1-2004 " (“POSIX.1”). IEEE Std The behavior is partially (but not completely) described in the System V Interface Definition, Fourth Edition (“SVID4”). Although it has never been formally standardized, the behavior described is largely portable across POSIX style systems, with two significant exceptions: the maximum length of the “#!” line, and the behavior if multiple arguments are passed. Please be aware that some operating systems limit the line to 32 or 64 characters, and that (as described above) the behavior in the face of multiple arguments is not consistent across systems. HISTORY The behavior of the kernel when encountering scripts that start in “#!” was not present in Version 7 AT&T UNIX. A Usenet posting to net.unix by Guy Harris on October 16, 1984 claims that the idea for the “#!” behavior was first proposed by Dennis Ritchie but that the first implementation was on BSD. Historical manuals (specifically the exec man page) indicate that the behavior was present in 4BSD at least as early as April, 1981. Information on precisely when it was first implemented, and in which version of UNIX, is solicited. SECURITY CONSIDERATIONS Numerous security problems are associated with setuid interpreter scripts. In addition to the fact that many interpreters (and scripts) are simply not designed to be robust in a setuid context, a race condition exists between the moment that the kernel examines the interpreter script file and the moment that the newly invoked interpreter opens the file itself. Because of these security issues, NetBSD does not allow setuid interpreter scripts by default. In order to turn on setuid interpreter scripts, options SETUIDSCRIPTS must be set in the configuration of the running kernel. Setting this option implies the FDSCRIPTS option, which causes the kernel to open the script file on behalf of the interpreter and pass it in argv as /dev/fd/[fdnum]. (See fd(4) for an explanation of the /dev/fd/[fdnum] devices.) This design avoids the race condition, at the cost of denying the interpreter the actual name of the script file. See options(4) for more information. However, the FDSCRIPTS mechanism is not a cure-all for security issues in setuid interpreters and scripts. Subtle techniques can be used to subvert even seemingly well written scripts. Scripts executed by Bourne type shells can be subverted in numerous ways, such as by setting the IFS variable before executing the script. Other interpreters possess their own vulnerabilities. Turning on SETUIDSCRIPTS is therefore very dangerous, and should not be done lightly if at all. NetBSD 3.0 May 6, 2005 3

miscellaneous information - NHL.com
User Manager Manual - intro to search (pdf) - UCAS
Version 7 Manual - Freiwald Software
apple-pascal-1.3-manual
Canon EOS ELAN 7/7E - EOS ELAN 7 Instruction Manual
2008 7 Series Owner's Manual - Irvine BMW
VINCI 7 Instruction manual - APart-Audio
QCapture PRO 7 User Manual - QImaging
HyChill Information Manual - HyChill Refrigerants
ST251 Oxyhandspa manual 7-2012 2.indd
Download Customary Fishing Information Manual - Ministry of ...
General informations and technical manual - Spatiul Construit
Information & Records Management Process Manual - University of ...
Download Exhibitor Services Manual (PDF) - Drug Information ...
uip165p owner's manual - Support Information Management System
Capitola Mall General information Criteria Manual - Macerich
Lakewood Center General Information Criteria Manual - Macerich
Information and Processing Manual Rheinspan® AirMaxx - Triplaco nv
Page 1 Page 2 THIS MANUAL DOES NOT SUPPLY INFORMATION ...
Engineering From 7 To 20 Tons Manual - Stulz Air Technologies Inc.
Samsung NP870Z5GE - NP870Z5G-S01US - User Manual (Windows 7) (ENGLISH)
Operations Manual - TE 7-C Rotary Hammer Drill - Home Depot
Honeywell 7-Day Programmable Thermostat (RTH7600D) - 7-Day Programmable Thermostat Operating Manual (English,French)
Honeywell 7-Day Programmable Thermostat (RTH7600D) - 7-Day Programmable Thermostat Operating Manual (English,French)
01 - General Information - The Old Car Manual Project
OWNER'S MANUAL & WARRANTY INFORMATION - ESP Guitars