Re: OpenPAM Figwort broke PAM modules from ports
From: Jeremie Le Hen (jeremie_at_le-hen.org)
Date: 06/29/05
- Previous message: Ulrich Spoerlein: "bsd.cpu.mk confusion"
- In reply to: Robert Watson: "Re: OpenPAM Figwort broke PAM modules from ports"
- Next in thread: Jeremie Le Hen: "Re: OpenPAM Figwort broke PAM modules from ports"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 29 Jun 2005 13:49:51 +0200 To: Robert Watson <rwatson@FreeBSD.org>
Hi Robert,
> Could you propose specific text to add to UPDATING, and I'll drop it in?
> Perhaps something along the lines of the following:
>
> Some previous versions of PAM have permitted the use of
> non-absolute paths in /etc/pam.conf or /etc/pam.d/* when referring
> to third party PAM modules in /usr/local/lib. A change has been
> made to require the use of absolute paths in order to avoid
> ambiguity and dependence on library path configuration, which may
> affect existing configurations.
This is perfect. Thank you very much.
Best regards,
-- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Ulrich Spoerlein: "bsd.cpu.mk confusion"
- In reply to: Robert Watson: "Re: OpenPAM Figwort broke PAM modules from ports"
- Next in thread: Jeremie Le Hen: "Re: OpenPAM Figwort broke PAM modules from ports"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|