This Patch is WIP
Current state: It used to allow restart of secure instance using keyring. Unfortunately after rebase it does not work. Still under investigation
Design is http://www.port389.org/docs/389ds/design/protect-NSS-db.html
Metadata Update from @tbordaz: - Pull-request tagged with: WIP
Actually my mistake sigh !!. The PR is working but during my test I provided the wrong password (need to take the one in generated by dscreate).
Remaining items...
rebased onto 77948634cf46f215a2dedeb5613efcd39dacabee
rebased onto 485d182ac9a7f4cba3a0b03e028ae0cfeb9a271d
rebased onto d93eea05698b513ff061611409aeab43e23195c8
rebased onto a739f4698eb4d0e38dea7a58eab0e0199a207da3
rebased onto ae45368c61f5dfa8ee2184580601d62eda137c94
rebased onto 31d5f752dc1f460dafb06456bdcbe0fb90d8083e
1 new commit added
ignore audit-ci
rebased onto 590f0ef90c24342609af8db0029d9ed3780974b6
2 new commits added
bz 1638875-7 : DS stores nss db password in keyring
bz 1638875-8 : DS stores nss db password in keyring
bz 1638875-9 : DS stores nss db password in keyring
bz 1638875-10 : DS stores nss db password in keyring
bz 1638875-11 : DS stores nss db password in keyring
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 pull request has been cloned to Github as issue and is available here: - https://github.com/389ds/389-ds-base/issues/3821
If you want to continue to work on the PR, please navigate to the github issue, download the patch from the attachments and file a new pull request.
Thank you for understanding. We apologize for all inconvenience.
Pull-Request has been closed by spichugi
This Patch is WIP
Current state: It used to allow restart of secure instance using keyring. Unfortunately after rebase it does not work. Still under investigation
Design is http://www.port389.org/docs/389ds/design/protect-NSS-db.html