Date: Wed, 9 May 2001 20:17:08 +0300 From: Peter Pentchev <roam@orbitel.bg> To: Kris Kennaway <kris@obsecurity.org> Cc: Rasputin <rara.rasputin@virgin.net>, Paul Herman <pherman@frenchfries.net>, security@FreeBSD.ORG Subject: Re: setkey(3) not present in the system Message-ID: <20010509201708.D497@ringworld.oblivion.bg> In-Reply-To: <20010509093849.B40205@xor.obsecurity.org>; from kris@obsecurity.org on Wed, May 09, 2001 at 09:38:50AM -0700 References: <20010509104313.A47276@dogma.freebsd-uk.eu.org> <Pine.BSF.4.33.0105091234310.79177-100000@husten.security.at12.de> <20010509114907.A48960@dogma.freebsd-uk.eu.org> <20010509135318.B44191@ringworld.oblivion.bg> <20010509042107.A36279@xor.obsecurity.org> <20010509143455.C44191@ringworld.oblivion.bg> <20010509093849.B40205@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 09, 2001 at 09:38:50AM -0700, Kris Kennaway wrote: > On Wed, May 09, 2001 at 02:34:55PM +0300, Peter Pentchev wrote: > > > > There's something nonstandard about the way it's linking which is > > > triggering all of the __warn_references() in libc regardless of > > > whether or not the code actually uses those "dangerous" functions -- I > > > don't know what it is, but I've seen it a lot in ports. It's probably > > > a bug which should be fixed. > > > > Nothing non-standard; the one about setkey() is triggered by just trying > > to resolve setkey against libc's setkey symbol; similarly for the f_prealloc() > > one. It's just that these warnings would never be triggered if the linker > > saw these symbols in another library, and saw no need to touch these particular > > object files within libc. > > Yes, I know you get the __warn_references() if you use a libc function > which has a __warn_references() line -- what happens here is that you > ALSO get *all* __warn_references() present in the entire library, even > if you don't use *any* of those functions, if you do the Weird Linker > Thing. Oh, I thought you meant this specific case. In this case, the original poster was referencing both f_prealloc() and setkey() in his program, so the warnings should be expected. G'luck, Peter -- I've heard that this sentence is a rumor. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010509201708.D497>