Hard Links between UNIX Utility Programs

[Bob Lenk]

> perhaps a simple example taken from real life.  I want to prevent users from
> examining the mailq using the /usr/ucb/mailq program because I feel that
> who a user sends mail to should not be subject to disclosure to others.

This is of little use, since "/usr/lib/sendmail -bp" is equivalent to
"mailq", even without the link.  Chris Torek's solution still applies; a
setgid program that disallows undesired options (including argv[0]) can
be used as a wrapper around the real sendmail program.

The real problem seems to be mixing functions to which different
privileges might apply in the same utility.  Whether these different
functions are specified by the name of the command, by an option,
interactively, or by any other means seems to be a side issue.

		Bob Lenk
		{ihnp4, hplabs}!hpfcla!rml
		rml%hpfcla at hplabs.hp.com