-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/2009 05:18 AM, Sumit Bose wrote:
On Wed, Oct 14, 2009 at 01:58:36PM -0400, Stephen Gallagher wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/13/2009 03:52 AM, Sumit Bose wrote:
On Mon, Oct 12, 2009 at 10:28:05AM -0400, Simo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/15/2009 04:25 AM, Sumit Bose wrote:
On Wed, Oct 14, 2009 at 08:18:33PM -0400, Simo Sorce wrote:
This is mostly cosmetic as for now we always ignore errors for users
lookups, and sssd_pam uses the pam_status errors to check for errors.
But I
On Wed, Oct 14, 2009 at 07:45:46PM -0400, Simo Sorce wrote:
On Fri, 2009-10-09 at 21:38 +0200, Sumit Bose wrote:
Hi,
with this patch the LDAP provider check typical attributes which
determines the lifetime of a password. If there is more than one scheme
available the following order is
On Thu, Oct 15, 2009 at 08:34:22AM -0400, Stephen Gallagher wrote:
Send a new patch, please. You have the infrastructure in place to test
it better than I can right now.
- --
Stephen Gallagher
RHCE 804006346421761
ok, new version attached, thanks again.
bye,
Sumit
From
On Thu, Oct 15, 2009 at 12:12:57PM +0200, Sumit Bose wrote:
On Wed, Oct 14, 2009 at 01:33:18PM -0400, Stephen Gallagher wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/14/2009 07:24 AM, Sumit Bose wrote:
Hi,
if auth_provider is set to a provider which can handle
On Thu, 2009-10-15 at 12:51 -0400, Stephen Gallagher wrote:
Most of these warnings are seen only on older platforms like RHEL5.
0001: Clean up warnings in pysss.c
Shouldn't we just use discard_const_p() in these cases ?
It doesn't look like the underlying code is ever going to change the
On 10/15/2009 01:24 PM, Simo Sorce wrote:
On Thu, 2009-10-15 at 12:51 -0400, Stephen Gallagher wrote:
Most of these warnings are seen only on older platforms like RHEL5.
0001: Clean up warnings in pysss.c
Shouldn't we just use discard_const_p() in these cases ?
It doesn't look like the
Hi,
Couple questions about async processing.
The communication usually consists of several parts. Imagine that you
have an object that is responsible for some sort of communication
(socket, pipe, file, bus - whatever).
Here are the basic things that can happen with such object:
* Object is
On Thu, 2009-10-15 at 18:00 +0200, Sumit Bose wrote:
ok, new version attached, thanks again.
ack and pushed
Simo.
--
Simo Sorce * Red Hat, Inc * New York
___
sssd-devel mailing list
sssd-devel@lists.fedorahosted.org
On Thu, 2009-10-15 at 18:05 +0200, Sumit Bose wrote:
ok, I've created a new patch (0002) with the changes, 0001 is
rebased
but unchanged. I've also added a 'deny' option for access_provider
and a
man page entry.
bye,
Sumit
Please find attached rebased versions.
ack and pushed
On Thu, 2009-10-15 at 14:14 -0400, Stephen Gallagher wrote:
On 10/15/2009 01:24 PM, Simo Sorce wrote:
On Thu, 2009-10-15 at 12:51 -0400, Stephen Gallagher wrote:
Most of these warnings are seen only on older platforms like RHEL5.
0001: Clean up warnings in pysss.c
Shouldn't we just
This patcheset does the minimal necessary work to separate
initialization from actual providers code for ldap and kerberos and uses
this to introduce a first basic ipa provider skeleton that simply reuses
the ldap and krb5 providers code.
Simo.
--
Simo Sorce * Red Hat, Inc * New York
From
12 matches
Mail list logo
