In article <20050317224218.GA7859@moray.salmi.ch>,
Jukka Salmi  <j+nbsd@2005.salmi.ch> wrote:
>Hi,
>
>on a current system built using todays sources, startx fails with
>
>	Fatal server error:
>	pam_start() failed.
>		Missing or mangled PAM config file or module?
>
>Syslog logs the following:
>
>	X: in openpam_configure(): No required or binding component in \
>	service xserver, facility auth
>
>Substituting 'binding' for 'sufficient' in /etc/pam.d/xserver (auth
>class) seems to fix the problem (but I'm not sure whether binding or
>required should be used, or if this matters at all).
>
>What recent PAM change causes this break? Why is a required or binding
>component needed now?

required is the correct change. I just committed it, thanks.
Our pam code has changed to be more strict in order to catch
accidental "default open" configurations.

christos