389-ds-base

#50734 lib389 creates non-SSCA cert DBs with misleading README.txt
Closed: wontfix by mhonek. Opened by mhonek.

Closed: wontfix
Reopen Issue

Issue Description

NssSsl always creates README.txt which describes the purpose of SSCA, even when creating only an instance-specific certificate database.

Package Version and Platform

1.4

Steps to reproduce

  1. dscreate an instance.
  2. Observe presence of README.txt in the /etc/dirsrv/slapd-

Actual results

The README.txt is present.

Expected results

The README.txt should not be there. Or, present with a different contents which however would be still misleading since the actual certificate database's files are mixed with other instance's files.

Commit ff75058b fixes this issue

7e39425a9..ae87936e4 389-ds-base-1.4.1 -> 389-ds-base-1.4.1

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: None (was: Fixed)

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/3789

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
Metadata

CLI lib389

None
None
None
None
None
Related Pull Requests
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.