In <[email protected]>, on 02/12/2013
at 09:04 AM, Charles Mills <[email protected]> said:
>Is my recollection correct?
The answer is "That depends."
Basic Unix associates with a file an owning user and group, along with
a set of permission bits. For a normal executable the user turns on
the executable bit for world. If he wants to restrict access, he only
turns on the executable for user and group, or only for user.
The user can also mark the executable as running under his own userid
when invoked by someone else. So if X is owned by FOO or by FOO's
group, and has the appropriate execute permission bit, and if Y is
owned by FOO and runs under FOO, the Y can invoke X on the user's
behalf. See the chmod command, including the s permission flag.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
Atid/2 <http://patriot.net/~shmuel>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
