cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
New Contributor

Insecure SHA1 Certificate

When running vulnerability scans against Windows computers running LogMeIn they trigger due to having a SHA1 generated certificate.

Upon further investigation the certificate was created by LogMeIn and is only available over port 2002.

 

Clients are running host 4.1.0.9954 

 

Is this something we have to wait for LogMeIn to fix and regenerate the certificates on each computer, or is this something we can fix locally?


Thank you!

1 REPLY
New Contributor

Re: Insecure SHA1 Certificate

Bump.

Is anyone else seeing this as well?