[Bug 1397250] Update Released

[Marcello Blancasio]

Thank you. libnss-ldap-264-2.2ubuntu4.14.04.2 fixed the issue.

On Thu, Nov 10, 2016 at 7:12 PM, Brian Murray <brian at ubuntu.com> wrote:
> The verification of the Stable Release Update for libnss-ldap has
> completed successfully and the package has now been released to
> -updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
> unsubscribed and will not receive messages about this bug report.  In
> the event that you encounter a regression using the package from
> -updates please report a new bug using ubuntu-bug and tag the bug report
> regression-update so we can easily find any regressions.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1397250
>
> Title:
>   SIGPIPE not caught in do_atfork_child()
>
> Status in nss_ldap:
>   Fix Released
> Status in libnss-ldap package in Ubuntu:
>   Fix Released
> Status in libnss-ldap source package in Trusty:
>   Fix Released
> Status in libnss-ldap source package in Xenial:
>   Won't Fix
> Status in libnss-ldap source package in Yakkety:
>   Won't Fix
>
> Bug description:
>   [Impact]
>
>    * If a process using libnss-ldap calls fork() and SIGPIPE was blocked,
>      the atfork() handler in the child process failed to catch the SIGPIPE
>      as it was supposed to do, that is in the call to  do_close_no_unbind().
>      So that, the uncaught SIGPIPE will be eventually delivered when the
>      child unblocks signals. This usually make the child process die
>      unexpectedly.
>
>    * This is only reproducible when ldap is configured for STARTTLS.
>
>    * Upstream fix has been long integrated.
>
>   [Test Case]
>
>    * See https://bugs.launchpad.net/ubuntu/trusty/+source/libnss-
>   ldap/+bug/1397250/comments/19
>
>
>   [Regression Potential]
>
>    * Fix has been upstream since 2010, and limited to path of child
>      forking, and SIGPIPE is blocked. No consequent bugs or regressions
>      in the upstream blamed on this change.
>
>
>   [Other Info]
>
>    * I'm currently limiting my SRU to trusty, as I'm unable to
>      recreate the bug on xenial.  Even so, I have tested the fixed
>      code on xenial to ensure there was no regression with the testcase.
>
>    * Will look at fixing xenial too, IFF someone comes forward able to
>      reproduce the bug/validate the fix.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nss-ldap/+bug/1397250/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1397250

Title:
  SIGPIPE not caught in do_atfork_child()

Status in nss_ldap:
  Fix Released
Status in libnss-ldap package in Ubuntu:
  Fix Released
Status in libnss-ldap source package in Trusty:
  Fix Released
Status in libnss-ldap source package in Xenial:
  Won't Fix
Status in libnss-ldap source package in Yakkety:
  Won't Fix

Bug description:
  [Impact]

   * If a process using libnss-ldap calls fork() and SIGPIPE was blocked, 
     the atfork() handler in the child process failed to catch the SIGPIPE 
     as it was supposed to do, that is in the call to  do_close_no_unbind().
     So that, the uncaught SIGPIPE will be eventually delivered when the
     child unblocks signals. This usually make the child process die
     unexpectedly.

   * This is only reproducible when ldap is configured for STARTTLS.

   * Upstream fix has been long integrated.

  [Test Case]

   * See https://bugs.launchpad.net/ubuntu/trusty/+source/libnss-
  ldap/+bug/1397250/comments/19

  
  [Regression Potential] 

   * Fix has been upstream since 2010, and limited to path of child
     forking, and SIGPIPE is blocked. No consequent bugs or regressions
     in the upstream blamed on this change.  

  
  [Other Info]
   
   * I'm currently limiting my SRU to trusty, as I'm unable to 
     recreate the bug on xenial.  Even so, I have tested the fixed 
     code on xenial to ensure there was no regression with the testcase.

   * Will look at fixing xenial too, IFF someone comes forward able to
     reproduce the bug/validate the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nss-ldap/+bug/1397250/+subscriptions