URL: https://github.com/SSSD/sssd/pull/1001
Author: sumit-bose
Title: #1001: ssh: fix matching rules default
Action: opened
PR body:
"""
Before the ssh_use_certificate_matching_rules option was added the ssh
responder returned ssh keys derived from all valid certificates. Since
the default of the ssh_use_certificate_matching_rules option is
'all_rules' in a case where no matching rules are defined all
certificated will be filtered out and no ssh keys are returned.
The intention of the default was to allow the same same certificates
which are allowed in the PAM responder for authentication. The missing
default matching rule which is currently use by the PAM responder if no
other rules are available is added by this patch.
There might still be a small regression in case certificates without the
extended key usage (EKU) clientAuth were used for ssh. In this case
'ssh_use_certificate_matching_rules = no_rules' or a suitable matching
rule must be added to the configuration.
Related to https://pagure.io/SSSD/sssd/issue/4121
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/1001/head:pr1001
git checkout pr1001
Hi,
I found the filtering of domain-local groups was implemented after a
change to query the group memberships from the LDAP server of the
domain the user belongs to instead of the global catalog, which had the
side effect of retrieving the DLGs of trusted domains [1].
This DLGs are cached but treated as non-POSIX gruops (no gid number
assigned and not returned), after the commit implementing the filter
[2].
I have found an use case where not filtering domain-local groups would
be useful. If you want to use group memberships in sudo rules to allow
temporary sudo access, the replication latency of global groups is very
high and can take up to 15 minutes, but using domain local groups
replication is done in less than one minute.
Would you willing to accept a patch adding a new parameter to disable
the filtering of DLGs?
Regards,
[1] https://pagure.io/SSSD/sssd/issue/2161
[2] https://pagure.io/SSSD/sssd/issue/2178
--
Samuel Cabrero / SUSE Labs Samba Team
GPG: D7D6 E259 F91C F0B3 2E61 1239 3655 6EC9 7051 0856
scabrero(a)suse.com
scabrero(a)suse.de
URL: https://github.com/SSSD/sssd/pull/993
Author: arkamar
Title: #993: configure: prefer python3 if available
Action: opened
PR body:
"""
We should prefer python3 every time when it is available regardless of
whether python3 binding are generated, otherwise `sbus_generate.sh` fails
in python3 only systems, where sssd is configured with
`--without-python3-bindings` parameter.
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/993/head:pr993
git checkout pr993
URL: https://github.com/SSSD/sssd/pull/998
Author: mzidek-gh
Title: #998: spec: Do not overwrite /etc/pam.d/sssd-shadowutils on update
Action: opened
PR body:
"""
We should not overwrite this file when sssd-common is
updated.
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/998/head:pr998
git checkout pr998
URL: https://github.com/SSSD/sssd/pull/979
Author: pbrezina
Title: #979: sdap: provide error message when password change fail in ldap_modify mode
Action: opened
PR body:
"""
Steps to reproduce:
1. Configure LDAP server to enable password constraints
2. Set ldap_pwmodify_mode = ldap_modify in [domain]
3. Run SSSD and authenticate as a user
4. Run passwd to change password, use password that does not meet requirements
It will print "password change successful" without this patch and server
error message with this patch applied.
Resolves:
https://pagure.io/SSSD/sssd/issue/4148
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/979/head:pr979
git checkout pr979
URL: https://github.com/SSSD/sssd/pull/996
Author: pbrezina
Title: #996: 1.16: failover: make sure we switch to anoter server if only port differs
Action: opened
PR body:
"""
This is a regression introduced in 735af71a8e169f17fa5462db610a1567c9618e29.
After this commit we checked only server name instead of name and port combo.
Steps to reproduce:
1. Configure SSSD to use two servers with same name but different ports
```
[domain/LDAP]
debug_level=0xFFF0
id_provider = ldap
ldap_uri = ldap://$SERVER1:12345,ldap://$SERVER1:389
ldap_tls_cacertdir = /etc/openldap/certs
ldap_search_base = dc=example,dc=com
```
2. The first server port is unreachable, the second is working.
3. Run sssd and try to resolve user.
4. Without the patch SSSD tries to connect to the first server twice
because new URI is not constructed and goes offline.
Resolves:
https://pagure.io/SSSD/sssd/issue/4112
Reviewed-by: Michal Židek <mzidek(a)redhat.com>
"""
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/996/head:pr996
git checkout pr996
URL: https://github.com/SSSD/sssd/pull/918
Title: #918: Add support for NSS hosts database lookup.
sumit-bose commented:
"""
Hi,
> Fixed, I have skipped `sssd-ldap-attributes.5.xml` because other `ldap_*_entry_usn` are not there either.
That's ok, thanks.
> I have also fixed a couple of issues I found while working in the networks support.
I guess there is a fair chance that there still might be some copy-and-paste issues like the ones you fixed.
Nevertheless, ACK.
Thank you for you patience.
bye,
Sumit
"""
See the full comment at https://github.com/SSSD/sssd/pull/918#issuecomment-594536408