[SSSD] [sssd PR#70][comment] check_duplicate: check name member before using it

2017-02-10 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/70 Title: #70: check_duplicate: check name member before using it lslebodn commented: """ On (10/02/17 08:35), Jakub Hrozek wrote: >I'm not sure if it's even possible to write an integration test because even >after the patch, sssd doesn't start, it

[SSSD] [sssd PR#70][comment] check_duplicate: check name member before using it

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/70 Title: #70: check_duplicate: check name member before using it jhrozek commented: """ I'm not sure if it's even possible to write an integration test because even after the patch, sssd doesn't start, it 'just' doesn't segfault. """ See the full

[SSSD] [sssd PR#70][+Accepted] check_duplicate: check name member before using it

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/70 Title: #70: check_duplicate: check name member before using it Label: +Accepted ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] [sssd PR#70][-Changes requested] check_duplicate: check name member before using it

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/70 Title: #70: check_duplicate: check name member before using it Label: -Changes requested ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] [sssd PR#145][+Pushed] Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/145 Title: #145: Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case Label: +Pushed ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To

[SSSD] [sssd PR#145][closed] Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/145 Author: jhrozek Title: #145: Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case Action: closed To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch

[SSSD] [sssd PR#145][comment] Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/145 Title: #145: Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case jhrozek commented: """ master: a5ecc93abb01cece628fdef04ebad43bba267419 sssd-1-14:

[SSSD] [sssd PR#145][comment] Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/145 Title: #145: Fix storing a sudoRule attriubute in a case-insensitive domain when the attriubute values differ only by case jhrozek commented: """ We can add a debug message about the duplicates, but unfortunately some admins had to keep the

[SSSD] [sssd PR#144][closed] SSSD does not start if using only the local provider and services line is empty

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/144 Author: fidencio Title: #144: SSSD does not start if using only the local provider and services line is empty Action: closed To pull the PR as Git branch: git remote add ghsssd https://github.com/SSSD/sssd git fetch ghsssd pull/144/head:pr144 git

[SSSD] [sssd PR#144][+Pushed] SSSD does not start if using only the local provider and services line is empty

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/144 Title: #144: SSSD does not start if using only the local provider and services line is empty Label: +Pushed ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] [sssd PR#144][comment] SSSD does not start if using only the local provider and services line is empty

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/144 Title: #144: SSSD does not start if using only the local provider and services line is empty jhrozek commented: """ master: 00c0b7bc6969d31deab9e8e7541b4a6483b78b3e 040ade7b2e11fecf615aedf58592cc7245900e86 """ See the full comment

[SSSD] [sssd PR#137][comment] Initial pkinit support

2017-02-10 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/137 Title: #137: Initial pkinit support lslebodn commented: """ On (09/02/17 02:50), sumit-bose wrote: >Thank you for running the tests, the valgirind issue was the same as the last >coverity warning. > The function get_pkinit_identity is defined inside

[SSSD] [sssd PR#144][comment] SSSD does not start if using only the local provider and services line is empty

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/144 Title: #144: SSSD does not start if using only the local provider and services line is empty jhrozek commented: """ Plus, probably nothing will change in this patch. """ See the full comment at

[SSSD] [sssd PR#144][+Accepted] SSSD does not start if using only the local provider and services line is empty

2017-02-10 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/144 Title: #144: SSSD does not start if using only the local provider and services line is empty Label: +Accepted ___ sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org To unsubscribe send an email to

[SSSD] Does anyone use id_provider=local ?

2017-02-10 Thread Jakub Hrozek
Hi, are there any SSSD users who actively use a configuration with: id_provider=local ? If so, what is your use-case? We're considering deprecating and eventually removing this provider upstream. The replacemant for id_provider=local would be id_provider=files:

[SSSD] Re: Watchdog, time shifts and scheduled events

2017-02-10 Thread Victor Tapia
El 10/02/17 a las 09:28, Jakub Hrozek escribió: > On Thu, Feb 09, 2017 at 09:50:18PM +0100, Victor Tapia wrote: I've been testing a scenario with a time shift of an hour to the past, and even though the watchdog detects the shift and restarts, the scheduled events are still stuck

[SSSD] Re: Watchdog, time shifts and scheduled events

2017-02-10 Thread Jakub Hrozek
On Thu, Feb 09, 2017 at 09:50:18PM +0100, Victor Tapia wrote: > >> I've been testing a scenario with a time shift of an hour to the past, > >> and even though the watchdog detects the shift and restarts, the > >> scheduled events are still stuck until the time passes. > > > >What kind of scheduled