Nicolas Williams wrote:
> On Tue, Jul 22, 2008 at 04:07:16PM -0700, Gary Winiger wrote:
>> Hummm, looking at the architecture of passwd(1), it only
>> supports 2 repositories. I suspect this is left over from some
>
> The question is: Is this architecture? Where is it written that
> passwd(1) has/must have this limitation? If it isn't a stated
> limitation then we'll simply fix this bug, otherwise we'll simply change
> that limitation.
>
> passwd(1) says:
>
> When a user has a password stored in one of the name ser-
> vices as well as a local files entry, the passwd command
> updates both. It is possible to have different passwords in
> the name service and local files entry. Use passwd -r to
> change a specific password repository.
>
> I don't think that implies a limit of two name service backends for the
> passwd database.
passwd(1) also says:
....
If all requirements are met, by default, the passwd command
consults /etc/nsswitch.conf to determine in which reposi-
tories to perform password update. It searches the passwd
and passwd_compat entries. The sources (repositories) asso-
ciated with these entries are updated. However, the password
update configurations supported are limited to the following
cases. Failure to comply with the configurations prevents
users from logging onto the system. The password update con-
figurations are:
o passwd: files
o passwd: files ldap
SunOS 5.11 Last change: 27 Aug 2007 2
User Commands passwd(1)
o passwd: files nis
o passwd: files nisplus
o passwd: compat (==> files nis)
o passwd: compat (==> files ldap)
passwd_compat: ldap
o passwd: compat (==> files nisplus)
passwd_compat: nisplus
....
Serge
>
> _______________________________________________
> sparks-discuss mailing list
> sparks-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/sparks-discuss
