- Joined
- Oct 13, 2018
- Messages
- 233
- Reaction score
- 9
Hello;
In my 3CX Debian distribution, I realize that the server come with a self signed X.509 certificate like this C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root and using SHA-1 With RSA Encryption as hashing algorithm. In order to do server hardening on this distribution, can I remove this self-signed certificate from the server in order to minimize the man-in-the-middle attack?
Also, how could I exclude sensitive HTTP headers from server responses that revealed server software information, including the following:
• PHP/7.2.6
• Apache/2.4.33 (Unix)
• OpenSSL/1.0.2o
Is there any negative impact on 3CX running if I close those vulnerability.
In my 3CX Debian distribution, I realize that the server come with a self signed X.509 certificate like this C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root and using SHA-1 With RSA Encryption as hashing algorithm. In order to do server hardening on this distribution, can I remove this self-signed certificate from the server in order to minimize the man-in-the-middle attack?
Also, how could I exclude sensitive HTTP headers from server responses that revealed server software information, including the following:
• PHP/7.2.6
• Apache/2.4.33 (Unix)
• OpenSSL/1.0.2o
Is there any negative impact on 3CX running if I close those vulnerability.