Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!sdd.hp.com!spool2.mu.edu!uunet!lll-winken!gauss.llnl.gov
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: Re: Suns 4.1 problems with X
Message-ID: <89141@lll-winken.LLNL.GOV>
Date: 10 Jan 91 17:26:12 GMT
Sender: usenet@lll-winken.LLNL.GOV
Organization: Lawrence Livermore National Laboratory
Lines: 25
Nntp-Posting-Host: gauss.llnl.gov


| From: vallone@oswego.Oswego.EDU (Daniel E. Vallone)
| 
| 	Why not just use the ldconfig program that comes with SunOS?

  I thought I had saved the article, but I can't find it.  I was informed
that ld.so would only retain SUID/SGID permissions on binaries whose
shared library references were resolved wholely from libraries in
/usr/lib, /usr/5lib, and /usr/local/lib (or libraries found in
directories specified with -Ldir.)  Unfortunately these restrictions and
exceptions aren't documented in ld(1).

  Is this restriction true/not true?  Even if I can has SUID/SGID objects
bound to libraries in other directories, I'd still want what I've
described because I want to have ld.so search a directory that I *don't*
want it to retain SUID/SGID permissions on.  I want to be able to specify
the following:

	/usr/lib		SUID|SGID
	/usr/5lib		SUID|SGID
	/usr/local/lib		SUID|SGID
	/usr/local/lib/X11	SUID|SGID
	/usr/new/lib		NOSUID|NOSGID

Casey