You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When changes are made to SSL configuration over LDAP, we should immediately store those changes in a model socket. In slapd_ssl_init2, when calling SSL_ImportFD, we should use the model socket argument. Then we don't have to do all of the SSL configuration in slapd_ssl_init2, that will be done by calling SSL_ImportFD with the model.
At startup, we should create the model socket from the configuration entries, then use the model socket to create the SSL listener sockets.
I'm not sure what we can do dynamically with SSL listener sockets. It may be possible to stop listening (remove the SSL listener fds from the poll list), then use SSL_ReconfigFD to reconfigure them with the latest SSL settings, then add them back.
The text was updated successfully, but these errors were encountered:
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48199
When changes are made to SSL configuration over LDAP, we should immediately store those changes in a model socket. In slapd_ssl_init2, when calling SSL_ImportFD, we should use the model socket argument. Then we don't have to do all of the SSL configuration in slapd_ssl_init2, that will be done by calling SSL_ImportFD with the model.
At startup, we should create the model socket from the configuration entries, then use the model socket to create the SSL listener sockets.
I'm not sure what we can do dynamically with SSL listener sockets. It may be possible to stop listening (remove the SSL listener fds from the poll list), then use SSL_ReconfigFD to reconfigure them with the latest SSL settings, then add them back.
The text was updated successfully, but these errors were encountered: