Re: [SSSD] Using path utils from libini_config

John Dennis wrote: > On 03/31/2010 06:03 PM, John Dennis wrote: >> On 03/31/2010 05:30 PM, Dmitri Pal wrote: >>> Hi, >>> >>> Is there any constraint on using path_utils from within the INI? >>> I need path to be converted to absolute path. >> >> That's what path_utils is there for, you should use i

Re: [SSSD] Using path utils from libini_config

On 03/31/2010 06:03 PM, John Dennis wrote: > On 03/31/2010 05:30 PM, Dmitri Pal wrote: >> Hi, >> >> Is there any constraint on using path_utils from within the INI? >> I need path to be converted to absolute path. > > That's what path_utils is there for, you should use it. The function is: > > int

Re: [SSSD] Using path utils from libini_config

On 03/31/2010 05:30 PM, Dmitri Pal wrote: > Hi, > > Is there any constraint on using path_utils from within the INI? > I need path to be converted to absolute path. That's what path_utils is there for, you should use it. The function is: int make_path_absolute(char *absolute_path, size_t absolute

[SSSD] Using path utils from libini_config

Hi, Is there any constraint on using path_utils from within the INI? I need path to be converted to absolute path. Ticket URL: -- Thank you, Dmitri Pal Engineering Manager IPA project, Red Hat Inc. --- Looking to carve

Re: [SSSD] [PATCH] Use SO_PEERCRED on the PAM socket

This goes to syslog, not debug logs. On Mar 31, 2010, at 4:38 PM, Simo Sorce wrote: > On Wed, 31 Mar 2010 15:29:58 -0400 > Stephen Gallagher wrote: > >> Nack. Please make the strings in ssscli_err2string() translatable. >> strerror() is already internationalized, we should be consistent. >> (Al

Re: [SSSD] [PATCH] Use SO_PEERCRED on the PAM socket

On Wed, 31 Mar 2010 15:29:58 -0400 Stephen Gallagher wrote: > Nack. Please make the strings in ssscli_err2string() translatable. > strerror() is already internationalized, we should be consistent. > (Also, we may eventually use these in places other than logger()) > > Otherwise, this looks great

Re: [SSSD] [PATCH] Make sss_userdel check for logged in users

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2010 07:12 AM, Jakub Hrozek wrote: > On 03/24/2010 10:09 PM, Stephen Gallagher wrote: >> In other words: > >> On platforms that support get_uid_table(): >> If the user is not logged in: >> 1) Delete the user. >> If the user is logged in: >>

Re: [SSSD] [PATCH] Use SO_PEERCRED on the PAM socket

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/29/2010 05:23 AM, Sumit Bose wrote: > Hi, > > please find attached my second attempt to exchange uid, gid and pid > between PAM client and responder. This new apporoach does not require > any communication between the client and the responder an

Re: [SSSD] Patch to fix LDAP ID backend GSSAPI credential expired messages

On Mon, 29 Mar 2010 19:41:57 +0400 Eugene Indenbom wrote: > Hi Simon, > > I have to admit that the patch is really quite big and, actually, it > has by far exceeded size and time limits I would normally apply to > patches to third party components. > > The patch can be theoretically split into

Re: [SSSD] PATCH] Add userdel_cmd param

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/24/2010 09:49 AM, Jakub Hrozek wrote: > On 03/23/2010 01:10 PM, Simo Sorce wrote: >> On Tue, 23 Mar 2010 11:59:22 +0100 >> Jakub Hrozek wrote: > >>> + >>> +cmd = talloc_asprintf(tctx, "%s %s", userdel_cmd, >>> +

Re: [SSSD] Patch to fix LDAP ID backend GSSAPI credential expired messages

On Wed, 31 Mar 2010 09:35:34 +0400 Eugene Indenbom wrote: > On 03/30/2010 10:58 PM, Simo Sorce wrote: > > > > Hi Eugene, > > There are still a few things that do not resonate here, but at this > > point I will have to go through the patch to be able to give back > > proper comments. I will try to

Re: [SSSD] #425

Stephen Gallagher wrote: > On 03/31/2010 10:01 AM, Dmitri Pal wrote: > > Hi, > > > If we want to fix #425 as proposed, should we fix #56 first or there is > > no need to do this and the password file should be edited manually? > > > We need to open a separate bug at some point on how we're actually

Re: [SSSD] #425

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2010 10:01 AM, Dmitri Pal wrote: > Hi, > > If we want to fix #425 as proposed, should we fix #56 first or there is > no need to do this and the password file should be edited manually? > We need to open a separate bug at some point on how w

[SSSD] #425

Hi, If we want to fix #425 as proposed, should we fix #56 first or there is no need to do this and the password file should be edited manually? -- Thank you, Dmitri Pal Engineering Manager IPA project, Red Hat Inc. --- Looking to carve out IT costs? www.redhat.com/

Re: [SSSD] [PATCHES] Do not revert options to defaults in SSSDConfig.get_domain()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2010 09:32 AM, Jakub Hrozek wrote: > On 03/31/2010 03:19 PM, Stephen Gallagher wrote: > >> Patch 0001: Add regression test to demonstrate the issue. > >> Patch 0002: There was a faulty check in get_domain() that led to the >> *_provider opti

Re: [SSSD] [PATCHES] Do not revert options to defaults in SSSDConfig.get_domain()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/31/2010 03:19 PM, Stephen Gallagher wrote: > > Patch 0001: Add regression test to demonstrate the issue. > > Patch 0002: There was a faulty check in get_domain() that led to the > *_provider options being re-added, sometimes after options relat

[SSSD] [PATCH] Fix typo in ldap_id_use_start_tls option description

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pushed to master under the one-liner rule. - -- Stephen Gallagher RHCE 804006346421761 Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ -BEGIN PGP SIGNATURE- Version: Gn

[SSSD] [PATCHES] Do not revert options to defaults in SSSDConfig.get_domain()

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Patch 0001: Add regression test to demonstrate the issue. Patch 0002: There was a faulty check in get_domain() that led to the *_provider options being re-added, sometimes after options related to them had already been set. If those options had a def

[SSSD] SELinux login management

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Adds a new option -Z to sss_useradd and sss_usermod. This option allows user to specify the SELinux login context for the user. On deleting the user with sss_userdel, the login mapping is deleted, so subsequent adding of the same user would result in t

Re: [SSSD] [PATCH] Make sss_userdel check for logged in users

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/24/2010 10:09 PM, Stephen Gallagher wrote: > In other words: > > On platforms that support get_uid_table(): > If the user is not logged in: > 1) Delete the user. > If the user is logged in: > 1) Delete the user. > 2) Print a message statin