From owner-freebsd-security Wed Jan 17 14: 8:10 2001 Delivered-To: freebsd-security@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 8152937B400 for ; Wed, 17 Jan 2001 14:07:50 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id DED8B2BBFC; Wed, 17 Jan 2001 16:07:39 -0600 (CST) Date: Wed, 17 Jan 2001 16:07:39 -0600 From: Bill Fumerola To: "David J. MacKenzie" Cc: freebsd-security@freebsd.org Subject: Re: full PAM support for login, rshd, and su Message-ID: <20010117160739.Q76347@elvis.mu.org> References: <20010117214735.E7DAD46BC@dagger.web.us.uu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010117214735.E7DAD46BC@dagger.web.us.uu.net>; from djm@web.us.uu.net on Wed, Jan 17, 2001 at 04:47:35PM -0500 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jan 17, 2001 at 04:47:35PM -0500, David J. MacKenzie wrote: > I think if you're going to ship PAM, you should actually use it. > The OpenSSH shipped with FreeBSD (as of 4.2-STABLE) is also missing > the USE_PAM support that's in the portable OpenSSH release. I highly > recommend importing that code into your source tree. I'm going to > have to do so in my tree. The openssh people have made life difficult for those trying to do work in this area by instantly forking all their code. Maybe thats just in their nature, though... -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message