While replication changelog encryption is not documented it is possible, and the UI should have a nice option to "enable/disable changelog encryption"
There is a doc on the wiki:
http://www.port389.org/docs/389ds/FAQ/changelog-encryption.html
And we should default to AES (notDES)
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 1.4.1
Metadata Update from @mreynolds: - Issue priority set to: normal
Metadata Update from @mreynolds: - Issue tagged with: Cockpit
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4.4 (was: 1.4.1)
Make sure CLI can do this as well
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/3169
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 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.