Warnings under OpenBSD

[Peter Galbavy]

The OpenBSD ld has these message built in as warnings about "unsafe"
well known functions. There is various literature on the safe use (or
really the unsafe use) of at least these, plus strcpy/strcat et al.

I still don't understand the setre*() race condition, since the
OpenBSD "gurus" are too arogant to explain or document these. The
attitude is one of "if you don't understand it, don't ask the
question." The mktemp() replacement mkstemp() removes the race
condition my returning you a file handle rather than a file name to
then open().

On Tue, Jun 08, 1999 at 06:18:24AM +1000, Christopher R. Hertel wrote:
> I've been fiddling with Samba on OpenBSD in an effort to help with the 
> trapdoor.c problem on that platform.  If I run ./configure under my own 
> account, the trapdoor.c test in never run.  As Dana pointed out, Samba 
> 2.0.4b then runs correctly under OpenBSD.  However, the following 
> compile-time warnings are generated (these are sorted and uniq'd):
> 
> lib/util_sec.o: warning: this program uses setregid(), which is deprecated.
> lib/util_sec.o: warning: this program uses setreuid(), which is deprecated.
> smbd/filename.o: warning: mktemp() possibly used unsafely; consider using mkstemp()
> smbd/message.o: warning: mktemp() possibly used unsafely; consider using mkstemp()
> smbd/reply.o: warning: mktemp() possibly used unsafely; consider using mkstemp()
> 
> These may be specific to OpenBSD.
> 
> Comments?
> 
> Chris -)-----
> 
> -- 
>              -- I have a shoehorn, the kind with teeth. --
>                                   ---
> Christopher R. Hertel -)-----                   University of Minnesota
> crh at nts.umn.edu              Networking and Telecommunications Services

-- 
Peter Galbavy
Knowledge Matters Ltd
http://www.knowledge.com/