sssd-devel May 2019

sssd-devel@lists.fedorahosted.org

3 participants
52 discussions

[sssd PR#730][+Accepted] confdb: sssd tools don't handle the implicit domain
by sumit-bose 22 May '19

22 May '19

URL: https://github.com/SSSD/sssd/pull/730 Title: #730: confdb: sssd tools don't handle the implicit domain Label: +Accepted

1 0

[sssd PR#730][comment] confdb: sssd tools don't handle the implicit domain
by sumit-bose 22 May '19

22 May '19

URL: https://github.com/SSSD/sssd/pull/730 Title: #730: confdb: sssd tools don't handle the implicit domain sumit-bose commented: """ Patch looks good and works fine for me. ACK """ See the full comment at https://github.com/SSSD/sssd/pull/730#issuecomment-494731392

1 0

[sssd PR#813][opened] SDAP: allow GSS-SPNEGO for LDAP SASL bind as well
by sumit-bose 21 May '19

21 May '19

URL: https://github.com/SSSD/sssd/pull/813 Author: sumit-bose Title: #813: SDAP: allow GSS-SPNEGO for LDAP SASL bind as well Action: opened PR body: """ From the LDAP client perspective GSS-SPNEGO and GSSAPI are quite similar. To support GSS-SPNEGO SSSD must make sure that a Kerberos ticket is available before the LDAP SASL bind is started. Related to https://pagure.io/SSSD/sssd/issue/4006 """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/813/head:pr813 git checkout pr813

3 15

[sssd PR#806][opened] sudo: always use server highest usn for smart refresh
by pbrezina 21 May '19

21 May '19

URL: https://github.com/SSSD/sssd/pull/806 Author: pbrezina Title: #806: sudo: always use server highest usn for smart refresh Action: opened PR body: """ The sudo attributes may not be indexed on the server, therefore if smart refresh filter is run on the server it may first search using the indexed entryusn attribute and run the rest of the filter on non-sudo objects. The number of objects that are filtered may increased dramatically if sudo rules are not changed for a long time (and thus keeping smaller and smaller last sudo usn number). This patch makes sure that highest sudo usn number is always set to the highest server usn number after each refresh. Resolves: https://pagure.io/SSSD/sssd/issue/3997 """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/806/head:pr806 git checkout pr806

3 26

[sssd PR#750][opened] Monitor: minor fixes
by alexey-tikhonov 20 May '19

20 May '19

URL: https://github.com/SSSD/sssd/pull/750 Author: alexey-tikhonov Title: #750: Monitor: minor fixes Action: opened PR body: """ """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/750/head:pr750 git checkout pr750

3 9

[sssd PR#804][opened] PAM: Also cache SSS_PAM_PREAUTH
by jhrozek 20 May '19

20 May '19

URL: https://github.com/SSSD/sssd/pull/804 Author: jhrozek Title: #804: PAM: Also cache SSS_PAM_PREAUTH Action: opened PR body: """ Related: https://pagure.io/SSSD/sssd/issue/3960 Even if cached_auth_timeout was set, the pam responder would still forward the preauthentication requests to the back end. This could trigger unwanted traffic towards the KDCs. """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/804/head:pr804 git checkout pr804

2 12

[sssd PR#815][opened] fix to not ignore/drop sudo "defaults" rule
by pzirnik 17 May '19

17 May '19

URL: https://github.com/SSSD/sssd/pull/815 Author: pzirnik Title: #815: fix to not ignore/drop sudo "defaults" rule Action: opened PR body: """ The "cn=defaults" rule does not require to have a sudoUser attribute, however with latest changes the defaults rule get dropped because of the missing sudoUser attribute. According to sudo ldap schema the attribute sudoUser is only a MAY not a MUST. Also when using the old pam/nss ldap library this is not an issue. I have seen no "cn=defaults" rule until now that does have a sudoUser attribute set, so i count this as a regression. My proposed patch does skip sysdb_sudo_add_lowered_users() if the rule name matches "defaults", which looks like the best possible approach for now. """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/815/head:pr815 git checkout pr815

2 3

[sssd PR#730][comment] confdb: sssd tools don't handle the implicit domain
by alexey-tikhonov 17 May '19

17 May '19

URL: https://github.com/SSSD/sssd/pull/730 Title: #730: confdb: sssd tools don't handle the implicit domain alexey-tikhonov commented: """ > @alexey-tikhonov, ping, would you like to continue the review or shall I? At that moment I was not sure I could ACK the patch, so I provided input I could and didn't assign it to me. Please, feel free to to review. """ See the full comment at https://github.com/SSSD/sssd/pull/730#issuecomment-493402831

1 0

[sssd PR#730][comment] confdb: sssd tools don't handle the implicit domain
by sumit-bose 17 May '19

17 May '19

URL: https://github.com/SSSD/sssd/pull/730 Title: #730: confdb: sssd tools don't handle the implicit domain sumit-bose commented: """ @alexey-tikhonov, ping, would you like to continue the review or shall I? """ See the full comment at https://github.com/SSSD/sssd/pull/730#issuecomment-493371339

1 0

[sssd PR#809][opened] sss_cache: Do nothing if SYSTEMD_OFFLINE=1
by thalman 15 May '19

15 May '19

URL: https://github.com/SSSD/sssd/pull/809 Author: thalman Title: #809: sss_cache: Do nothing if SYSTEMD_OFFLINE=1 Action: opened PR body: """ Running `rpm-ostree compose tree` results in a big spam. This is because rpm-ostree doesn't want scripts writing into `/var`; it's system-administrator managed state. Let's just silently do nothing if we're running offline, as there won't be a sssd running. The original suggestion can be found here: https://pagure.io/SSSD/sssd/pull-request/3959 """ To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/809/head:pr809 git checkout pr809

2 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

sssd-devel May 2019