Hi,
I have been working on sssd being able to flush hosts from it's cache.
Here is an initial patch to add the options to the cli of sss_cache.
I have noticed that there are some methods already in src/db/sysdb_ssh.c
like sysdb_update_ssh_known_host_expire: Does that seem like the right
function to call to expire a host?
Advice is appreciated.
--
William Brown <william(a)firstyear.id.au>
Hello,
attached patch is the first of many to solve
https://fedorahosted.org/sssd/ticket/1991
"The return codes of various sysdb operations differ. Some search
operations would return ENOENT if they don't find a matching object some
would return EOK but an empty result list."
I think it would be best if in case that no results were found both
ENOENT value and 'properly' empty list were returned.
Thank for opinions or/and review.
Pavel Reichl
ehlo,
In theory, it could be possible to build current master without samba
on rhel5, but the spec file would be very complicated.
It is better to simplify spec file.
Patch is attached.
1 file changed, 43 deletions(-) :-)
LS
Hi,
this patch contains the libwbclient implementation for SSSD to allow
Samba file-servers and utilities to use SSSD instead of winbind to map
SIDs, names and POSIX IDs. The related ticket is
https://fedorahosted.org/sssd/ticket/1588.
The SSSD specific calls can be found in files with '_sssd' as part of
the name, the other files are mainly taken from the original Samba
sources because they contain API calls which are independent of the
backend. I have made some minor modification to meet the SSSD coding
style but tried to avoid major changes to make a diff to the original
version more easy. If major issue are found during review I think it
would be a good idea to try to bring the changes back to samba as well.
In wbc_pwd_sssd.c instead of linking in the related sources of the NSS
client I dlopen-ed libnss_sss.so.2 to have more flexibility about where
and how to build the library. I you think this is too much overhead I'd
be happy to change the code to use the NSS client call directly.
The patch does not contain unit test because the Samba source code
already contains some basic tests. I'll try to work with the samba
package maintainer to make this code in a samba-devel or samba-test
package available so that it can be used by SSSD as well.
Basic functional test can be run manually with wbinfo, e.g.:
$ /usr/bin/wbinfo -n 'AD18\Administrator'
S-1-5-21-3090815309-2627318493-3395719201-500 SID_USER (1)
$ /usr/bin/wbinfo -S S-1-5-21-3090815309-2627318493-3395719201-500
1670800500
bye,
Sumit
Hi,
these two patches implement the MIT Kerberos localauth plugin for SSSD.
Since it uses the new plugin style
(http://k5wiki.kerberos.org/wiki/Projects/Plugin_support_improvements)
it has to be activated explicitly. A section like
[plugins]
localauth = {
module = sssd:/path/to/plugin/sssd_krb5_localauth_plugin.so
enable_only = sssd
}
Should work. Please note that this example deactivates any other
mechanism, e.g. .k5login files. See krb5.conf man page of MIT Kerberos
1.12 how to active the mechanism as well.
One of the main use cases for this plugin is an IPA environment with
trust to AD. Currently AD user who want to use SSO with IPA client needed
a .k5login file in their home directory containing their Kerberos
principal. Alternatively krb5.conf has to be edited but here the names
user at the login prompt has to follow a fixed format and are case
sensitive. If the localauth plugin is activated the mapping of Kerberos
principal and user name is done by SSSD.
While I was testing the plugin with ssh I found that st least the Fedora
and RHEL versions of the sshd do not rely completely in the Kerberos
libraries here but do some checks on their own, especially they check
for the existence of the .k5login file in the default configuration.
This check can be disabled by setting KerberosUseKuserok to 'no' but
then sshd does not call krb5_userok() but the more restrictive
krb5_aname_to_localname() and does case sensitive checks on the related
names which won't help much in out case. As a result a .k5login file is
still needed when testing with ssh but it can be empty or contain random
content. I will investigate why OpenSSH is patched in this way on Fedora
and RHEL.
bye,
Sumit