389-devel September 2009

389-devel@lists.fedoraproject.org

5 participants
37 discussions

Start a nNew thread

Please Review: Add minimum SSF setting
by Nathan Kinder 30 Sep '09

30 Sep '09

2 2

pushed man page fix
by Rich Megginson 30 Sep '09

30 Sep '09

I updated the setup-ds.pl man page with the new update options and documentation. To ssh://git.fedorahosted.org/git/389/ds.git 5d91896..7cd8196 master -> master

1 0

Re: [Bug 526141] allow empty groups
by Rich Megginson 30 Sep '09

30 Sep '09

bugzilla(a)redhat.com wrote: > Please do not reply directly to this email. All additional > comments should be made in the comments box of this bug. > > > https://bugzilla.redhat.com/show_bug.cgi?id=526141 > > > Noriko Hosoi <nhosoi(a)redhat.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |nhosoi(a)redhat.com > Devel Whiteboard|comment#1.review? |comment#1.review+nhosoi > Thanks - pushed to master

1 0

Please review: Bug 526141 - allow empty groups
by Rich Megginson 30 Sep '09

30 Sep '09

https://bugzilla.redhat.com/show_bug.cgi?id=526141 Resolves: bug 526141 Bug Description: allow empty groups Reviewed by: ??? Fix Description: Change groupOfNames and groupOfUniqueNames to allow empty groups by changing the member/uniqueMember attribute from MUST to MAY. NOTE: This is the way it was before 1.2.1 changed it. Also note that this is a temporary hack until we solve the problem of LDAP grouping with a better solution, one that eases migration of existing installations. Platforms tested: RHEL5 x86_64 Flag Day: no Doc impact: no https://bugzilla.redhat.com/attachment.cgi?id=363112&action=diff

1 0

Re: [Bug 520921] Config schema not included in core schema
by Rich Megginson 30 Sep '09

30 Sep '09

bugzilla(a)redhat.com wrote: > Please do not reply directly to this email. All additional > comments should be made in the comments box of this bug. > > > https://bugzilla.redhat.com/show_bug.cgi?id=520921 > > > Nathan Kinder <nkinder(a)redhat.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |nkinder(a)redhat.com > Devel Whiteboard|comment#5.review? |comment#5.review+nkinder > Thanks - pushed to master

1 0

Please review: Bug 520921 - Config schema not included in core schema
by Rich Megginson 29 Sep '09

29 Sep '09

https://bugzilla.redhat.com/show_bug.cgi?id=520921 Resolves: bug 520921 Bug Description: Config schema not included in core schema Reviewed by: ??? Fix Description: Just had to move a few schema from 02common and 30ns-common into 01core389.ldif. I also added 01core389.ldif to the list of schema installed when install_full_schema=0 is specified with setup-ds.pl. I also added these schema files to the list of schema files to upgrade. With these changes, the server starts up fine. The only error is this: [29/Sep/2009:16:47:53 -0600] - Entry "cn=PAM Pass Through Auth,cn=plugins,cn =config" has unknown object class "pamConfig" This is because the pam pass through plugin is included in the default config. I'd rather not move that schema file. That plugin can be removed from the default config during setup by specifying a slapd.ConfigFile directive with contents like this: dn: cn=PAM Pass Through Auth,cn=plugins,cn=config changetype: delete Platforms tested: RHEL5 x86_64 Flag Day: no Doc impact: no https://bugzilla.redhat.com/attachment.cgi?id=363060&action=diff

2 1

Re: [Bug 526319] SASL IO sometimes loops with "error: would block"
by Rich Megginson 29 Sep '09

29 Sep '09

bugzilla(a)redhat.com wrote: > Please do not reply directly to this email. All additional > comments should be made in the comments box of this bug. > > > https://bugzilla.redhat.com/show_bug.cgi?id=526319 > > > Nathan Kinder <nkinder(a)redhat.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |nkinder(a)redhat.com > Devel Whiteboard|comment#1.review? |comment#1.review+nkinder > Thanks - pushed to master

1 0

Please review: Bug 526319 - SASL IO sometimes loops with "error: would block"
by Rich Megginson 29 Sep '09

29 Sep '09

https://bugzilla.redhat.com/show_bug.cgi?id=526319 Resolves: bug 526319 Bug Description: SASL IO sometimes loops with "error: would block" Reviewed by: ??? Fix Description: The semantics for recv() are that it returns -1 for errors, 0 for connection closed, and non-zero for some bytes received. The sasl code w as not using those semantics - it was returning 0 for successful read and -1 for error. Although I have not been able to reproduce the exact failure, what I be lieve is happening is that the initial read of the packet length in sasl_io_star t_packet() works, and the sasl IO is received. At some point, the connection is closed by the client, and the PR_Recv return of 0 is not handled correctly, and somehow the errno gets set to EWOULDBLOCK. From this point on, PR_Recv() wi ll return -1 (since the socket has been closed) and errno is not reset from EWOU LDBLOCK. The fix is to make sure the sasl IO code handles the PR_Recv() return value correctly. Note that with CONNS (8) error log level, you may still occasionally see "wo uld block" errors, but as long as they are not endlessly repeating, this should be ok. Platforms tested: RHEL5 x86_64 Flag Day: no Doc impact: no https://bugzilla.redhat.com/attachment.cgi?id=363058&action=diff

2 1

Re: [Bug 525785] setup-ds-admin.pl should use correct default hostname + port
by Rich Megginson 25 Sep '09

25 Sep '09

bugzilla(a)redhat.com wrote: > Please do not reply directly to this email. All additional > comments should be made in the comments box of this bug. > > > https://bugzilla.redhat.com/show_bug.cgi?id=525785 > > > Nathan Kinder <nkinder(a)redhat.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |nkinder(a)redhat.com > Devel Whiteboard|comment#1.review? |comment#1.review+nkinder > thanks - pushed to master

1 0

Please review: [Bug 525007] ldif2db replaces existing modify/create name and timestamps
by Ulf Weltman 25 Sep '09

25 Sep '09

Summary: ldif2db replaces existing modify/create name and timestamps https://bugzilla.redhat.com/show_bug.cgi?id=525007 [Problem Description] LDIF that is imported might contain createTimestamp, creatorsName, modifyTimestamp, or modifiersName. The import code since FDS 1.2 inserts these attributes but it should only do so if they're missing; any existing values should take precedence. [Fix Description] Only insert the attributes if they don't already exist in the entry. attrlist_find() rather than slapi_entry_attr_find() is used because the latter reports attributes with empty values as being missing attributes. [Proposed Fix] https://bugzilla.redhat.com/attachment.cgi?id=362157

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-devel September 2009