Date: Sun, 20 Oct 1996 09:04:14 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-hackers@freebsd.org (FreeBSD hackers) Cc: dnelson@emsphone.com, deraadt@theos.com Subject: Re: cvs commit: src/lib/libc/db/hash hash_buf.c Message-ID: <199610200704.JAA27667@uriah.heep.sax.de> In-Reply-To: <199610200201.TAA03344@phaeton.artisoft.com> from Terry Lambert at "Oct 19, 96 07:01:11 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Terry Lambert wrote: > Well, you would hope that you could set the flag locally, where it's > supported, and it would be globally supported. > > Basically, you'd have a linker set initialization function for an > affected library, and when the program started, it would call the > setup functions, which would in turn obey the flag, if set. linker set... linker set. Well, the requirement of this application for the `secure free' is already known at compile time. Shouldn't it be possible to just link another free() (kinda `overloaded') in this case, thus eliminating any peculiarities of any flag testing? (I've trimmed the Cc list to those who were in the list of addressees, but are IMHO not on freebsd-hackers. If you guys are not interested in this technical discussion, say so, and we'll drop you from there.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610200704.JAA27667>