>
> On Mon, Dec 05, 2011 at 12:37:35PM +0100, Jan Zelený wrote:
> > > Hi,
> > >
> > > I'm hoping someone can help. I am using RHEL 6.1 and trying to
> > > use sssd to
> > > authenticate to our ldap server.
> > >
> > > Our ldap server uses the uid=name@domain as the uid. sssd seems
> > > to pass
On Mon, 2011-12-05 at 13:44 -0500, Stephen Gallagher wrote:
> Glib fails if the NULL-terminator is included when a length is
> specified.
>
> I recently pushed "Allow using Glib for UTF8 support" after doing
> excessive negative testing. However, I forgot to do positive testing and
> therefore fai
Glib fails if the NULL-terminator is included when a length is
specified.
I recently pushed "Allow using Glib for UTF8 support" after doing
excessive negative testing. However, I forgot to do positive testing and
therefore failed to discover that Glib treats a NULL-terminator as an
error in valida
On Mon, 2011-12-05 at 11:09 -0500, Simo Sorce wrote:
> On Mon, 2011-12-05 at 11:06 -0500, Stephen Gallagher wrote:
> > On Mon, 2011-12-05 at 09:30 -0500, Stephen Gallagher wrote:
> > > On Fri, 2011-12-02 at 15:16 -0500, Simo Sorce wrote:
> > > > - Original Message -
> > > > > Currently, SSS
On Mon, 2011-12-05 at 13:27 +0100, Jakub Hrozek wrote:
> On Fri, Dec 02, 2011 at 04:27:53PM +0100, Jan Zelený wrote:
> > This might be contributing to some segfaults in the failover code:
> >
> > https://fedorahosted.org/sssd/ticket/1037
> >
> > Thanks
> > Jan
>
> Ack, nice catch. This was proba
Hi,
>> This may result in a change in our strategy going forward. I'm looking
>> for users to describe to us the reasons why they're choosing SSSD (in
>> its current incarnation) over winbind. What I'm trying to sort out is
>> whether there are specific *issues* with winbind that SSSD is solving
>
On Mon, 2011-12-05 at 11:06 -0500, Stephen Gallagher wrote:
> On Mon, 2011-12-05 at 09:30 -0500, Stephen Gallagher wrote:
> > On Fri, 2011-12-02 at 15:16 -0500, Simo Sorce wrote:
> > > - Original Message -
> > > > Currently, SSSD only supports using libunistring to manage unicode
> > > > st
On Mon, 2011-12-05 at 09:30 -0500, Stephen Gallagher wrote:
> On Fri, 2011-12-02 at 15:16 -0500, Simo Sorce wrote:
> > - Original Message -
> > > Currently, SSSD only supports using libunistring to manage unicode
> > > strings. There are some platforms out there (such as RHEL 5) that do
> >
On 12/04/2011 02:08 PM, Steven Jones wrote:
> Hi,
>
> What about strategic reasons and not tactical ones?
>
> I know this may not be the case in this instance, but, personally I hate
> doing short term "mangles" to make things workI'd much rather bite the
> bullet and go for a "better" long
On Fri, 2011-12-02 at 15:16 -0500, Simo Sorce wrote:
> - Original Message -
> > Currently, SSSD only supports using libunistring to manage unicode
> > strings. There are some platforms out there (such as RHEL 5) that do
> > not
> > have libunistring available. With this patch, we add an opt
On Mon, Dec 05, 2011 at 03:01:29PM +0100, Jakub Hrozek wrote:
> The attached patch syncs up with Samba commit
> 50e30afa608dfdeae8a260730ead9761ed424dad
I haven't tested the patch, but the change looks as expected.
ACK (without testing)
bye,
Sumit
___
The attached patch syncs up with Samba commit
50e30afa608dfdeae8a260730ead9761ed424dad
From ad5acb51ce31d72f2d6442637201afc1e6c0bd15 Mon Sep 17 00:00:00 2001
From: Jakub Hrozek
Date: Mon, 5 Dec 2011 12:19:12 -0500
Subject: [PATCH] Always attempt to connect in sdap_async_sys_connect_done
This sync
On Fri, Dec 02, 2011 at 04:27:53PM +0100, Jan Zelený wrote:
> This might be contributing to some segfaults in the failover code:
>
> https://fedorahosted.org/sssd/ticket/1037
>
> Thanks
> Jan
Ack, nice catch. This was probably the cause, because the next/prev
pointers were mismatched and the cra
Hi,
What about strategic reasons and not tactical ones?
I know this may not be the case in this instance, but, personally I hate doing
short term "mangles" to make things workI'd much rather bite the bullet and
go for a "better" long term engineered solution...I find doing things that way
On Mon, Dec 05, 2011 at 12:37:35PM +0100, Jan Zelený wrote:
> > Hi,
> >
> > I'm hoping someone can help. I am using RHEL 6.1 and trying to use sssd to
> > authenticate to our ldap server.
> >
> > Our ldap server uses the uid=name@domain as the uid. sssd seems to pass the
> > name part only. Below
> Hi,
>
> I'm hoping someone can help. I am using RHEL 6.1 and trying to use sssd to
> authenticate to our ldap server.
>
> Our ldap server uses the uid=name@domain as the uid. sssd seems to pass the
> name part only. Below is the extract from log. This is generated by
> running getent passwd ste
Hi,
I'm hoping someone can help. I am using RHEL 6.1 and trying to use sssd to
authenticate to our ldap server.
Our ldap server uses the uid=name@domain as the uid. sssd seems to pass the
name part only. Below is the extract from log.
This is generated by running getent passwd ste...@lsd.com
O
17 matches
Mail list logo
