diff options
| author | Jakub Hrozek <jhrozek@redhat.com> | 2014-08-12 10:32:33 +0200 |
|---|---|---|
| committer | Jakub Hrozek <jhrozek@redhat.com> | 2014-10-14 11:04:41 +0200 |
| commit | 5ecab6dc08ac35a400e067af09b49e7fcb0f17c0 (patch) | |
| tree | 7efb876b1dba2068ce38d55c95a42d8c414632e9 /src/providers/ldap/sdap_async.c | |
| parent | 567093719cba804366d49b8e27562bad192c6f71 (diff) | |
| download | sssd-5ecab6dc08ac35a400e067af09b49e7fcb0f17c0.tar.gz sssd-5ecab6dc08ac35a400e067af09b49e7fcb0f17c0.tar.xz sssd-5ecab6dc08ac35a400e067af09b49e7fcb0f17c0.zip | |
IPA: handle searches by SID in apply_subdomain_homedir
https://fedorahosted.org/sssd/ticket/2391
apply_subdomain_homedir() didn't handle the situation where an entity
that doesn't match was requested from the cache. For user and group
lookups this wasn't a problem because the negative match was caught
sooner.
But SID lookups can match either user or group. When a group SID was
requested, the preceding LDAP request matched the SID and stored the
group in the cache. Then apply_subdomain_homedir() only tried to search
user by SID, didn't find the entry and accessed a NULL pointer.
A simple reproducer is:
$ python
>>> import pysss_nss_idmap
>>> pysss_nss_idmap.getnamebysid(group_sid)
The group_sid can be anything, including Domain Users (XXX-513)
Reviewed-by: Michal Židek <mzidek@redhat.com>
(cherry picked from commit 82347f452febe3cbffc36b0a3308ffb462515442)
Diffstat (limited to 'src/providers/ldap/sdap_async.c')
0 files changed, 0 insertions, 0 deletions