From owner-freebsd-security Tue Oct 10 7: 5:56 2000 Delivered-To: freebsd-security@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 16F0537B503 for ; Tue, 10 Oct 2000 07:05:48 -0700 (PDT) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id VAA51626; Tue, 10 Oct 2000 21:04:53 +0700 (NSS) (envelope-from fjoe@iclub.nsu.ru) Date: Tue, 10 Oct 2000 21:04:53 +0700 (NSS) From: Max Khon To: "Nick A. Leuta" Cc: FreeBSD-Security Subject: Re: PAM help needed In-Reply-To: <00bb01c032ab$3ee9ccc0$131fa8c0@skynick> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi, there! On Tue, 10 Oct 2000, Nick A. Leuta wrote: > > > My questions are: > > > a. Is any of my assumptions/conclusions wrong? > > > b. Is there any work done on the subject to fix it? > > > c. How stable is PAM on FreeBSD? > > > d. Any known problems that you know from your experience? > > I do not know of any problems with PAM under FreeBSD. > > Seems that FreeBSD PAM library is taken without any > > significant modifications from Linux PAM 0.65 distribution. > > Yes, it's true. But unlike FreeBSD, under Linux RH 6.x distribution all > applications like login, passwd, su, vlock, xdm, xlock, xscreensaver (in > /etc/pam.d also mentioned shutdown, xsaver...) using pam. to support passwd we should add support for this to our modules. Seems that nobody really wanted to have such functionality (I haven't seen patches for this). same thing with su. do not know about X stuff. > ...Do FreeBSD's pam_* modules realize all known (auth, account, session, > password) "module-types"? no. most modules implement only auth (and some of them implement account) module types /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message