The SSL certificate algorithm & FIPS‐140 compliant
674481Apr 21 2010 — edited Apr 29 2010I am not sure if this is the right location for this thread:
We have started to upgrade our databases to Oracle 11g R2 from 10 and 11g R1. But before than, our technical people are saying we need fix some or all the vunurability and compliant issues with our server before we start.
I don't know where to start, can anyone suggest where we can start from. Please see few of the messages we got from scanning machines:
Synopsis : The remote host is not FIPS‐140 compliant. Description : The encryption setting used by the remote Terminal Services service is not FIPS‐140 compliant. Solution : Change RDP encryption level to : 4. FIPS Compliant Risk factor : Low / CVSS Base Score : 2.6 (CVSS2#AV:N/AC:H/Au:N/C:P/I:N/A:N) Plugin output : The terminal services encryption level is set to : 3. High
Synopsis : The SSL certificate has been signed using a weak hash algorithm. Description : The remote service uses an SSL certificate that has been signed using a cryptographically weak hashing algorithm ‐ MD2 MD4 or MD5. These algorithms are known to be vulnerable to collision attacks.