#49282 389 directory server crashed after Qualys scan
Closed: wontfix Opened by samz.

Here's output by debugging core dump file:
gdb /usr/sbin/ns-slapd core.21041
....
Core was generated by `/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-instance -i /var/run/dirsrv/slapd-instance '.
Program terminated with signal 11, Segmentation fault.
#0 0x00007fc87d37a6c1 in memcpy () from /lib64/libc.so.6

389 version:
389-ds-base-libs-1.2.11.15-89.el6.x86_64
389-ds-base-1.2.11.15-89.el6.x86_64

OS version:
CentOS release 6.6 (Final)

Steps to reproduce

Qualys scan again

Actual results

389 directory server crashed again

Expected results

389 directory server crashed again


Metadata Update from @samz:
- Issue private status set to: False (was: True)

This is fixed in the "nss" package via: https://access.redhat.com/errata/RHSA-2017:1364

Metadata Update from @mreynolds:
- Custom field type adjusted to defect
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2341

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 Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata