How to correctly convert an ssl certificate from .pem to .pfx?

Question

IIS

There is a sertbot on the nginx server that pulls certificates from letsencrypt.

As a result of working out the bot, a directory with .pem keys appeared

`privkey.pem` : the private key for your certificate.
`fullchain.pem`: the certificate file used in most server software.
`chain.pem` : used for OCSP stapling in Nginx >=1.3.7.
`cert.pem` : will break many server configurations, and should not be used
without reading further documentation (see link below).

As a result, a lock appears on the site, the browser does not swear, it shows that this connection uses the TLS 1.2 protocol.

For the IIS server, I convert .pem to pfx with the command:

openssl pkcs12 -export -out myname.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem

I bind the resulting pfx to the server, but the key converted for the locale looks like this

and when I view the page code in the browser I see this:

The connection used to load resources from https://name.domain.ru used TLS 1.0 or TLS 1.1 , which are deprecated and will be disabled in the future. Once disabled, users will be prevented from loading these resources. The server should enable TLS 1.2 or later. See https://www.chromestatus.com/feature/5654791610957824 for more information.

Why is there a TLS 1.2 certificate in nginx, but in IIS locale after converting TLS 1.1?

Answer 1

Because the certificate is in no way associated with the TLS version.
You need to enable TLS 1.2 support in IIS and disable TLS 1.0, TLS 1.1 and SSLv3.

Answer 2

The certificate does not depend on tls, only how you configure the webserver

Answer 3

encryption is not properties of the certificate, but web server settings....