> > > These entries are generated at server startup (there is no way to prevent > that). So stop the server and edit the dse.ldif and remove these entries, > then start the server up and those errors will go away - well until you renew > the server cert again :-)
It's worth pointing out that we do have an open issue about this: https://pagure.io/389-ds-base/issue/49525 It also may be worth us investigating disabling attr encryption in newly created instances since it's not a default-used feature IMO. > >> >> >> >> _______________________________________________ >> 389-users mailing list -- >> [email protected] >> >> To unsubscribe send an email to >> [email protected] >> >> Fedora Code of Conduct: >> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> >> List Guidelines: >> https://fedoraproject.org/wiki/Mailing_list_guidelines >> >> List Archives: >> https://lists.fedoraproject.org/archives/list/[email protected] > -- > > 389 Directory Server Development Team > > _______________________________________________ > 389-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/[email protected] — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
