The self-Signed https certificate is insecure.

The self-Signed https certificate is insecure.

I. project requirements

All the apps we make are enterprise-level applications, while downloading enterprise-level applications must follow the itms protocol, and https links are required under the itms protocol. This requires your server to support the https protocol, this protocol requires an SSL certificate. We use a self-signed certificate during the test, and the self-signed certificate is inherently insecure, since the update of ios10.3, even if a self-signed certificate is installed, an error is reported, indicating that the app cannot be downloaded because Apple has blocked untrusted certificates.

Ii. Solutions

1. For a self-signed certificate, you must manually open the Trust for the certificate. For general purpose, choose local> Certificate Trust Settings> certificate open trust.

2. To apply for a trusted Certificate, such as a StartCom certificate, it will certainly be very expensive. For the list of trusted root certificates available in ios, refer to the official documents of apple.

Https://support.apple.com/zh-cn/HT208125

Iii. Why is the self-signed certificate insecure?

1,Self-signed documents are most vulnerable to SSL man-in-the-middle attacks

The self-signed certificate is a certificate that is not trusted by the browser. When you access the self-signed certificate, the browser will warn you that the certificate is untrusted and you need to manually confirm whether the certificate is trusted. All websites that use self-signed documents clearly tell users that, in this case, users must trust and continue browsing! This creates an opportunity for man-in-the-middle attacks.

2,Self-signed documents support insecure SSL communication re-negotiation mechanism

Almost all servers that use self-Signed SSL certificates have insecure SSL communication and re-negotiation security vulnerabilities. This is a security vulnerability of the SSL protocol, because the self-signed certificate system does not track the latest technology and does not promptly fill in the missing information! This vulnerability can be exploited by hackers to intercept users' encrypted information, such as bank accounts and passwords. It is dangerous and must be fixed in time.

3. Use insecure 1024-bit asymmetric key pairs in self-signed documents

At present, almost all self-signed certificates are 1024-bit and self-Signed root certificates are 1024-bit. Of course, they are not safe. In other words: Because the self-Signed SSL certificate is deployed, professional guidance from professional SSL certificate providers cannot be obtained, and the 1024-bit security is no longer known.

4. The validity period of the Self-signed certificate is too long.

Another common problem in self-signed documents is that certificates are valid for a long period of time, namely, 5 years and 20 or 30 years, they also use insecure 1024-bit encryption algorithms. It may be because you don't need any money when creating a self-signed certificate, but you don't know why the PKI Technical Standard restricts the validity period of the certificate. The longer the validity period, the more likely it is to be cracked by a hacker, because he has enough time (20 years) to crack your encryption.