From owner-freebsd-security Wed May 9 9:38:54 2001 Delivered-To: freebsd-security@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-108.dsl.lsan03.pacbell.net [63.207.60.108]) by hub.freebsd.org (Postfix) with ESMTP id D105637B422 for ; Wed, 9 May 2001 09:38:50 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 413FD678BA; Wed, 9 May 2001 09:38:50 -0700 (PDT) Date: Wed, 9 May 2001 09:38:50 -0700 From: Kris Kennaway To: Peter Pentchev Cc: Rasputin , Paul Herman , security@FreeBSD.ORG Subject: Re: setkey(3) not present in the system Message-ID: <20010509093849.B40205@xor.obsecurity.org> References: <20010509104313.A47276@dogma.freebsd-uk.eu.org> <20010509114907.A48960@dogma.freebsd-uk.eu.org> <20010509135318.B44191@ringworld.oblivion.bg> <20010509042107.A36279@xor.obsecurity.org> <20010509143455.C44191@ringworld.oblivion.bg> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="E39vaYmALEf/7YXx" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010509143455.C44191@ringworld.oblivion.bg>; from roam@orbitel.bg on Wed, May 09, 2001 at 02:34:55PM +0300 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --E39vaYmALEf/7YXx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > Nothing non-standard; the one about setkey() is triggered by just trying > to resolve setkey against libc's setkey symbol; similarly for the f_preal= loc() > 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 part= icular > 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. Kris --E39vaYmALEf/7YXx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD4DBQE6+XKZWry0BWjoQKURArFzAKC2XxHCZqRxV6QyISFJykoJuSf9UQCY7SEP H+ZM7UUfc0HeDYeOmfXjow== =bQRA -----END PGP SIGNATURE----- --E39vaYmALEf/7YXx-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message