From owner-freebsd-security Wed May 9 3:53:52 2001 Delivered-To: freebsd-security@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id DC49F37B422 for ; Wed, 9 May 2001 03:53:48 -0700 (PDT) (envelope-from roam@ringworld.nanolink.com) Received: (qmail 44369 invoked by uid 1000); 9 May 2001 10:53:18 -0000 Date: Wed, 9 May 2001 13:53:18 +0300 From: Peter Pentchev To: Rasputin Cc: Paul Herman , security@freebsd.org Subject: Re: setkey(3) not present in the system Message-ID: <20010509135318.B44191@ringworld.oblivion.bg> Mail-Followup-To: Rasputin , Paul Herman , security@freebsd.org References: <20010509104313.A47276@dogma.freebsd-uk.eu.org> <20010509114907.A48960@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010509114907.A48960@dogma.freebsd-uk.eu.org>; from rara.rasputin@virgin.net on Wed, May 09, 2001 at 11:49:07AM +0100 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 09, 2001 at 11:49:07AM +0100, Rasputin wrote: > * Paul Herman [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.. /me shudders at the memory of the recent -current stdio internals change, and the horrible fate of programs that assumed too much.. G'luck, Peter -- This sentence no verb. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message