db2ldif crashes when we set '-a LDIF_PATH' to a place that can't be accessed by the user (dirsrv by default)
dirsrv
389-ds-base-1.4.4.3-20200624git6a2750c02.fc32
Run:
db2ldif -Z localhost -s "dc=example,dc=com" -a /root/db.ldif
Exported ldif file: /root/db.ldif [25/Jun/2020:08:55:15.147935611 +0000] - INFO - slapd_exemode_db2ldif - db2ldif - Backend Instance(s): [25/Jun/2020:08:55:15.154173408 +0000] - INFO - slapd_exemode_db2ldif - db2ldif - userroot
/usr/sbin/db2ldif: line 170: 13355 Segmentation fault (core dumped) /usr/sbin/ns-slapd db2ldif -D /etc/dirsrv/slapd-localhost -s "dc=example,dc=com" -a /root/db.ldif
It should report an error and it should not crash
https://pagure.io/389-ds-base/pull-request/51191
Metadata Update from @spichugi: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Metadata Update from @spichugi: - Issue assigned to spichugi
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1806978 - Issue priority set to: normal - Issue set to the milestone: 1.4.3
98a8287e4..20e24cc03 master -> master 0f97891f6..8ff268f1e 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
Metadata Update from @spichugi: - 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/4241
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)