After we switched to writing pidfile after the responders started, we forgot
that starting a second SSSD instance would first overwrite the pipes and
sockets and only then the SSSD would find out there already is a pidfile.
Another one liner. If no rules were passed to
sdap_sudo_rules_refresh_send (if rules was NULL) and no error
occurred, then variable ret was used uninitialized. This is not very
likely to happen, but it is safer to have it initialized.
Maybe we should consider adding initialization of all "ret" variables to
our coding guidelines to avoid these "unlikely but possible" errors in
Patch 01: The debug_level variable was set before the parameters were
processed, so the default debug level was used no matter what number was
specified with --debug.
Patch 02: When interactive input fails, error message should be displayed.
Patch 03: When file is used to specify a password in sss_seed, then only
first line of this file is used. Also empty passwords are treated as
errors. (My local test environment is broken so I have not tested this,
please test it when reviewing.)
Patches are in attachment.
now that SSSD supports OpenSSH formatted public keys, the OpenSSH-LPK
<http://code.google.com/p/openssh-lpk/> schema is automatically
supported as well in the LDAP provider. All you have to do is to set the
ldap_user_ssh_public_key option in your LDAP domain section of sssd.conf
Currently there is no default value for ldap_user_ssh_public_key in LDAP
domains. Does it make sense to make sshPublicKey the default value for it?