#3424 calling nspr_nss_setup/cleanup repeatedly in sss_encrypt SIGABRTs NSS eventually
Closed: Fixed Opened by jhrozek.

This is probably a NSS bug, but we're not making it any easier on us by calling setup and teardown of NSS on each encrypt. We should just remove the cleanup totally or clean up on responder shutdown.


Metadata Update from @jhrozek:
- Issue assigned to jhrozek

The fix is now part of https://github.com/SSSD/sssd/pull/225

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.3

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1460689

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1460689

Issue linked to Bugzilla: Bug 1460689

Metadata Update from @jhrozek:
- Issue priority set to: major

There is already a PR, but it is being reviewed and upstream needs to release the next version quite soon. Therefore I'm moving this ticket to the next version.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)

Metadata Update from @jhrozek:
- Issue tagged with: PR

master:

  • a6f606117e5cfe64c4b49f94e514bf82054716d3

Metadata Update from @lslebodn:
- Issue close_status updated to: Fixed
- Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.4)
- Issue status updated to: Closed (was: Open)

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4451

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata