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=518514
>
>
> 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
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=516305
>
>
> Noriko Hosoi <nhosoi(a)redhat.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |nhosoi(a)redhat.com
> Devel Whiteboard| |comment#18.review+nhosoi
>
>
>
>
> --- Comment #19 from Noriko Hosoi <nhosoi(a)redhat.com> 2009-09-24 12:52:52 EDT ---
> Your fix looks good. Thanks, Rich!
>
Thanks - pushed to master
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=513308
>
>
> Noriko Hosoi <nhosoi(a)redhat.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |nhosoi(a)redhat.com
> Devel Whiteboard|comment#3.review? |comment#4.review+nhosoi
>
Thanks - pushed to master
https://bugzilla.redhat.com/show_bug.cgi?id=513308
Resolves: bug 513308
Bug Description: empty principal name used when using server to server
sasl for db chaining
Reviewed by: ???
Fix Description: Change the logic to check if the username is a valid
principal name. A valid principal name in this context will be a
non-empty string that does not contain the '=' character (which will be
a bind DN in this context).
Platforms tested: RHEL5 x86_64
Flag Day: no
Doc impact: no
https://bugzilla.redhat.com/attachment.cgi?id=362330&action=diff
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=519455
>
>
> Nathan Kinder <nkinder(a)redhat.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |nkinder(a)redhat.com
> Devel Whiteboard|comment#6.review? |comment#6.review+nkinder
>
Thanks - pushed to master
https://bugzilla.redhat.com/show_bug.cgi?id=519455
Resolves: bug 519455
Bug Description: Should not attempt to pop SASL IO layer if not
using SASL IO
Reviewed by: ???
Fix Description: Before attempting to pop the SASL IO layer from the
prfd,
first make sure we are using sasl IO, the prfd is not NULL, and the prfd
has a SASL IO layer on it.
This also fixes a bug with setting nsslapd-localhost in the
bootstrap code -
if you are using a system that does not have DNS configured
correctly, you
may want to force the SASL code to use the nsslapd-localhost for the
FQDN.
Platforms tested: RHEL5 x86_64
Flag Day: no
Doc impact: no
https://bugzilla.redhat.com/attachment.cgi?id=362324&action=diff
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=518279
>
>
> Nathan Kinder <nkinder(a)redhat.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |nkinder(a)redhat.com
> Devel Whiteboard|comment#2.review? |comment#2.review+nkinder
>
>
Thanks - pushed to master