Subject: Re: PAM enabled on head
To: Arto Huusko <arto.huusko@utu.fi>
From: Quentin Garnier <cube@cubidou.net>
List: current-users
Date: 03/08/2005 17:00:51
--ssZxAlvqSOvXAj81
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 08, 2005 at 05:18:32PM +0200, Arto Huusko wrote:
> On Tue, 8 Mar 2005, Quentin Garnier wrote:
>=20
> > Speaking of which, there is an issue for people like me who compile with
> > MKKERBEROS=3Dno.  That way, pam_krb5.so is not built, but yet it is ref=
erenced
>=20
> Have the set lists been fixed for MKKERBEROS=3Dno case? When PAM
> was initally commited, I did a build with MKKERBEROS=3Dno, but the
> set lists still referenced pam krb modules. IIRC, I haven't seen
> a commit to fix this.

Yes, they were, it was confirmed by my build.  It did choke on the skey
module, but I fixed it then.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--ssZxAlvqSOvXAj81
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (NetBSD)

iQEVAwUBQi3MM9goQloHrPnoAQLPQwf5ARcADVGkojQMpaBn83CmiAlHXaOLT2xb
f41Yyfslfy5qG0KtZHXtgXRGalgsXCXpXcfMATpJGBR3YYmVqbC8mT4NepwcmKuE
2XBM0tg7VpW4nm4OjPpyOA/yoyNHyWXlgR7+G0HSpGdcYSXpfwE5JKHl50FNh5dn
sPbUHeNkABpZfo+c0HlSCw77tKOm8rSSeDhzJzJvRnmsS6GKfFaCe5mZgAhZ/nu4
C4RPB5+0sDhcYG5Qt6wX2yHYjzxIPa8m5gYEDdsm3NI/7FzadP/i3hkaLOfpBwvw
iV17Ff81Syore2GKRXmuFh7vrlfWQPwhEib9QFFmUPFOU/ChcitrWQ==
=jHh3
-----END PGP SIGNATURE-----

--ssZxAlvqSOvXAj81--