SCSP has been using the SHA1 hashing algorithm since version 5.2.4. Any installation made since that version is therefore secure. However, if a manager has been upgraded from an earlier version such as 5.0.x or 5.1.x, it will retain the original certificates. This can be verified by checking the signing algorithm according to HOWTO59835. In that case, the following unsupported procedure can be used to generate new SHA1 compliant certificates.
"openssl.exe", Certificate tool, found in: C:\Program Files (x86)\Symantec\Critical System Protection\Server\tools
"keytool.exe", Keystore and cert tool, found in: C:\Program Files (x86)\Symantec\Critical System Protection\server\jre\bin
"agent-cert.ssl" and "server-cert.ssl", SCSP Certificate/Keystores found in: C:\Program Files (x86)\Symantec\Critical System Protection\server
"server.xml", SCSP Certificate Configuration file found in: "C:\Program Files (x86)\Symantec\Critical System Protection\server\tomcat\conf"
"keystorepass", Keystore password found in: server.xml
- Back up old certs to "agent-cert.ssl.ori" and "server-cert.ssl.ori".
- Run Keytool to generate a new Keystore and certificate:
- command: "keytool -genkey -alias sss -keyalg RSA -keystore server-cert.ssl -validity 5000 -keysize 2048"
- When prompted, enter KeystorePass password from server.xml or create a new strong password.
- First and last name: SCSP_Management_Server.
- OU: <server_hostname>.
- Other details optional.
- Run Keytool to generate Certificate Signing Request file.
- command: "keytool -certreq -alias sss -keystore server-cert.ssl -file fim.csr"
- Run Keytool to export new certificate from new keystore
- command: "keytool -export -alias sss -keystore server-cert.ssl -file exp.crt"
- Run keytool to generate new agent cert from certificate:
- command: "keytool.exe -export -Alias sss -rfc -keystore server-cert.ssl -file agent-cert.ssl "
- Copy new "agent-cert.ssl" and "server-cert.ssl" to "C:\Program Files (x86)\Symantec\Critical System Protection\server".
- Stop SCSP Management Server service
- Only if new a new keystore password was used in step 2b, edit server.xml and replace keystorepass with new version (appears 3 separate times in the file)
- Restart management server service
- Log in to SCSP Console.
- Accept the new certificate.
- Copy "agent-cert.ssl" to all SCSP agents.
- If IPS is running, restore the null policy (this can be done locally by running "sisipsconfig -r").
- On each agent, run "sisipsconfig -c agent-cert.ssl". It is advisable to test thoroughly on one or more agents before rolling out elsewhere.
- Run "sisipsconfig -t" to test the connection.