From owner-freebsd-security Wed Apr 22 11:51:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14868 for freebsd-security-outgoing; Wed, 22 Apr 1998 11:51:30 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14822 for ; Wed, 22 Apr 1998 18:51:14 GMT (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id UAA04423; Wed, 22 Apr 1998 20:49:54 +0200 (CEST) To: "Matthew N. Dodd" cc: Nate Williams , Peter Wemm , freebsd-security@FreeBSD.ORG Subject: Re: Static vs. dynamic linking (was Re: Using MD5 insted of DES ...) In-reply-to: Your message of "Wed, 22 Apr 1998 14:42:13 EDT." Date: Wed, 22 Apr 1998 20:49:54 +0200 Message-ID: <4421.893270994@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk In message , "Matthew N. Dodd" writes: >On Wed, 22 Apr 1998, Poul-Henning Kamp wrote: >> I disagree, I think just the crypt problem is sufficient argument to >> go dynamic. > >But its not really the only way to skin the cat. > >You could have something like authd running and listening on a unix domain >socket and handeling non /etc/passwd auth requests. > >(Yes its ugly, but in a different way.) What about the root password prompt in /sbin/init ? That is the only really troublesome case... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message