How to secure IBM SDS with TLS 1.2 and GSKit certificates

preview_player
Показать описание
IBM SDS was formerly known as IBM Tivoli Directory Server, or ITDS. We are using a self-signed X.509 SSL Certificate.

dn: cn=SSL, cn=Configuration
changetype: modify
replace: ibm-slapdSslAuth
ibm-slapdSslAuth: serverAuth

dn: cn=SSL, cn=Configuration
changetype: modify
replace: ibm-slapdSecurity
ibm-slapdSecurity: TLS

dn: cn=SSL, cn=Configuration
changetype: modify
replace: ibm-slapdSslKeyDatabase

dn: cn=SSL, cn=Configuration
changetype: modify
replace: ibm-slapdSslCertificate
ibm-slapdSslCertificate: serverlabel

dn: cn=SSL, cn=Configuration
changetype: modify
replace: ibm-slapdSslCipherSpec
ibm-slapdSslCipherSpec: AES

dn: cn=SSL, cn=Configuration
changetype: modify
replace: ibm-slapdSecurityProtocol
ibm-slapdSecurityProtocol: TLS12

dn: cn=SSL, cn=Configuration
changetype: modify
add: ibm-slapdSSLExtSigalg
ibm-slapdSSLExtSigalg: GSK_TLS_SIGALG_ECDSA_WITH_SHA512
Рекомендации по теме
Комментарии
Автор

Hopefully it didn't take you 10 months to solve this, but in the video the "ibm-slapdSecurity" value is set to "SSL", in the text of the video description it's set to "TLS". TLS will ONLY accept startTLS communication and not start the secure port, while "SSL" will. "SSLTLS" starts both. He does a great job of explaining those options in the video but the text in the video description is wrong for start 636 listening.

evilbilbo
Автор

done all the changes but nothing is running under 636 port

rohitsingam