This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SHA-2 certificate in SEC 5.5.0

Hi,
We have upgraded SEC from version 5.4.0 to 5.5.0 specifically to avail of the SHA-2 certificate used by the RMS components which was introduced in 5.4.1 as per KB article 125162. However it looks like 5.5.0 is still using the old SHA-1 certificate.

Does this mean we should have installed 5.4.1 first rather than going straight to 5.5.0? Is there a way round this or do we need to uninstall 5.5.0 and install 5.4.1 (I really hope not!) Or have I just missed something?

Thanks in advance,
Justin

This thread was automatically locked due to age.

0 Peter Dudas over 7 years ago in reply to Vikas

Hi Vikas!

We are in the same shoes. Nessus scanner marks 8194/tcp ports as insecure due to weak signature algorithm and unknown CA.

Cac.pem (EM2_CA) is using MD5 hash algorithm.

Do you have a solution to update it to an SHA2 cert and make it trusted by the endpoints (without reinstalling SEC)?

We have SEC 5.5.0 installed.

Thank you!

Peter Dudas
Cancel
Vote Up 0 Vote Down

Cancel
0 Vikas over 7 years ago in reply to Peter Dudas

Hi Peter,

Please open a case with us as it would be advisable to be in touch with us should things go astray(no they won't, I'm just scaring ya)

I've requested Gowtham to get in touch with you via DM so that we can get the Case ID.

Thanks,

Vikas
Cancel
Vote Up 0 Vote Down

Cancel
0 Gagan Singh over 6 years ago in reply to Vikas

We have the same issue.

Sophos Enterprise Console 5.5.0

Still using SHA1 cert.

Is there an easy way to re-issue SAH2 rather than a full reinstall?
Cancel
Vote Up 0 Vote Down

Cancel
0 QC over 6 years ago in reply to Gagan Singh

Hello Gagan Singh,

as prvious responses suggest please contact Support. SEC is still 5.5.0, SEC versions are "stable", i.e. there are no in-version patches or changes.

Christian
Cancel
Vote Up 0 Vote Down

Cancel