Date: Wed, 9 May 2001 04:21:07 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Peter Pentchev <roam@orbitel.bg> 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: <20010509042107.A36279@xor.obsecurity.org> In-Reply-To: <20010509135318.B44191@ringworld.oblivion.bg>; from roam@orbitel.bg on Wed, May 09, 2001 at 01:53:18PM %2B0300 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>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Wed, May 09, 2001 at 01:53:18PM +0300, Peter Pentchev wrote: > On Wed, May 09, 2001 at 11:49:07AM +0100, Rasputin wrote: > > * Paul Herman <pherman@frenchfries.net> [010509 11:41]: > > > On Wed, 9 May 2001, Rasputin wrote: > > > > > > > Anybody know where I can get these functions? > > > > Thanks. > > > > > > > > /usr/lib/libc.so: WARNING! setkey(3) not present in the system! > > > > /usr/lib/libc.so: WARNING! des_setkey(3) not present in the system! > > > > /usr/lib/libc.so: WARNING! encrypt(3) not present in the system! > > > > /usr/lib/libc.so: WARNING! des_cipher(3) not present in the system! > > > > > Just follow your nose, it always knows! :-) > > > des_setkey(3) manpage mentions -lcipher. Looks like it's in > > > > If you could see the size of my nose, you'd be even more amazed I missed this.. > > Someone else mentioned -lcipher, I'll throw that in and give it a whirl. > > > > Thanks. > > > > Incidentally, (and OT-ly), this is my favourite error message... > > > > > /usr/lib/libc.so: warning: this program uses f_prealloc(), which is stupid. > > The fact that the message sounds interesting is quite OT; however, the fact > that it states could be quite important - see my other e-mail on the subject. > It seems that the writers of the WAP gateway in question are trying to do > something in a way too smart for their own good.. 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. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6+SgjWry0BWjoQKURAj9IAKCTThKcCZXFdg0ZXhlqlIeK7EY5+wCfZs2F ZBzLwmaTVSoq0eoxiJxLeeM= =6UAA -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010509042107.A36279>