Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Dec 2003 00:24:05 +0100
From:      des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=)
To:        Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc:        freebsd-current@freebsd.org
Subject:   Re: NSS and PAM
Message-ID:  <xzpllpwceay.fsf@dwp.des.no>
In-Reply-To: <200312012250.hB1MoCMZ081007@khavrinen.lcs.mit.edu> (Garrett Wollman's message of "Mon, 1 Dec 2003 17:50:12 -0500 (EST)")
References:  <20031129011334.GC88553@madman.celabo.org> <xzpbrqw7xsb.fsf@dwp.des.no> <20031201142737.GC99428@madman.celabo.org> <xzp7k1geb6x.fsf@dwp.des.no> <20031201175925.GC244@madman.celabo.org> <xzpvfp0ch1z.fsf@dwp.des.no> <200312012250.hB1MoCMZ081007@khavrinen.lcs.mit.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Wollman <wollman@khavrinen.lcs.mit.edu> writes:
> <<On Mon, 01 Dec 2003 23:24:40 +0100, des@des.no (Dag-Erling =3D?iso-8859=
-1?q?Sm=3DF8rgrav?=3D) said:
> > The problem is that the authentication information needs to be stored
> > somewhere, and the usual solution is to store it in the directory,=20
> ...which is usually the worst possible place.  Please don't penalize
> those of us with sensible authentication systems.

You're the one trying to penalize other people.  A common framework
for directory and authentication services can of course store
authentication tokens separately from user information, but the
reverse isn't true.  You can't unilaterally decide to leave out
functionality that 90% of our users require just because you are in a
position to use (what you consider to be) a better solution.

DES
--=20
Dag-Erling Sm=F8rgrav - des@des.no



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpllpwceay.fsf>