Ping a Specific Port

Question

lepe

Asked: 2021-11-11 21:06:03 +0800 CST2021-11-11 21:06:03 +0800 CST 2021-11-11 21:06:03 +0800 CST

NET::ERR_CERT_AUTHORITY_INVALID with self-signed CA in Windows

772

I created a (self-signed) root certificate and signed a web server certificate using a system I developed in Java (the web certificate is used in Apache 2.4.41).

The certificates work without issues in Linux and Mac (tested in different Webkit browsers and Firefox). The certificate and the server setup scores A+ using testssl.sh.

The CA certificate is correctly installed without any warning, but not accepted (still showing the red-triangle warning and the NET::ERR_CERT_AUTHORITY_INVALID error) in Windows (tested with 2 Windows 10 devices, one which is a fresh install). Tested in Chrome, Edge and Firefox.

I have tried many things:

installing them using certlm.msc, certutil.exe, through settings or by double-clicking the files
either Local or User scope
regenerating the root certificate with different settings
changing Apache settings
restarting browsers and the computers
stopping antivirus software

I have read related questions in this site (none seems to fix it) and I have look into other websites for solutions, but without success.

This is a fake CA certificate generated by the same system (with the same settings, except the key length here is 1024 to reduce the size of this post):

Key and Certificate:

CA Summary

Version: 3
         SerialNumber: 6873848332899071428
             IssuerDN: CN=Fake Authority,C=US,ST=CA,L=LA,O=Example LTD,OU=None,[email protected]
           Start Date: Thu Nov 11 06:06:53 JST 2021
           Final Date: Fri Nov 11 00:00:00 JST 2022
            SubjectDN: CN=Fake Authority,C=US,ST=CA,L=LA,O=Example LTD,OU=None,[email protected]
           Public Key: RSA Public Key [b8:07:ef:1f:8e:91:c0:ab:12:db:38:3f:76:e7:0a:7f:21:9d:fe:49],[56:66:d1:a4]
        modulus: 983fc7e042334c460e2682a9ce61fbcdf0ae367f1d5c5a67b1872bb83fb1c6b87ef175290b800eac7e8837de8713696798428e602c8018169086dc13431dfc2eacad24564b8fc47a800f4601492b693948d0b42f54082340ca734c52ef2f4246a7283c5594b7b9dc51ebb04591a60cc61b362a9c6a68230967e720f441ee4815
public exponent: 10001

  Signature Algorithm: SHA256WITHRSA
            Signature: 610d8fbef7d049ef56b46ea9789e01e766c6d4cc
                       ec53e8c4f71738a1611fbde924a633a467875b93
                       cf6005578066c4b175f7dc41f14fc91284f6fb9b
                       62b77dc6e7a6500184e7567232a25631ac05471b
                       57755d5ee9ad4e4c7d6a2a4b3ad686f0b51b9104
                       ec1ea145b82ab3928022c1dd58665ca55e609895
                       869bc90b1ce2fcc2
       Extensions: 
                       critical(true) BasicConstraints: isCa(true)
                       critical(true) KeyUsage: 0x6
                       critical(false) 2.5.29.14 value = DER

Server Certificate

Cert Summary

Version: 3
         SerialNumber: 6648705147606043571
             IssuerDN: CN=Fake Authority,C=US,ST=CA,L=LA,O=Example LTD,OU=None,[email protected]
           Start Date: Thu Nov 11 06:08:37 JST 2021
           Final Date: Fri Nov 11 00:00:00 JST 2022
            SubjectDN: CN=fake.example.com,C=US,ST=CA,L=LA,O=Example LTD,OU=None,[email protected]
           Public Key: RSA Public Key [2e:cd:8e:16:02:6f:b3:27:16:01:21:cb:1a:2b:9b:27:18:71:86:87],[56:66:d1:a4]
        modulus: 8cccc3f04931d04dac6eaed7e71455572d79c33a4a251b68ae0381fb2a43eb8b3676e2f968142537e77c2c4f661527dca4230f98e7cbd7a84c3c42396138731131eb5679a10c1f9eb6ba16a46fc4be280ad037b49987dbf0ed317b3b0882220fec59c95ef3b8fd1134a736d6783341cc43eb3e00e5f48c32c35805b4f305e4d215c038732f69aaa70b736823de3f8e842812572d682a5486ba2f92698322b247b9fa6552d31d26baa4ce1ad47f328792c95304b7931c01c780d757e392636226d996a558deb2e7b3d3480c8375f7d722027269a9296fa7ae5230b254305169da458ad3f4bc8274e8e354237063013584782a21803e664fce3691405c3d1bc99d
public exponent: 10001

  Signature Algorithm: SHA256WITHRSA
            Signature: 88dd18b477a5ba113a2145a18a2d2a87e520dfff
                       f8340bdb76ae9da8c7ca68063b803253c7b519fa
                       6df302eb122cab39e30d86529e2d9810c7fa6012
                       e2be299ba3dad80b5f04fc8e6ee4ab2abc86becd
                       ee5565de54ecef3ee3ef1469ff91fd17b881d7fb
                       789de3d3688fe1df3029ebdf51f0fc55cb9d771f
                       66ad6aa5b8211929
       Extensions: 
                       critical(true) BasicConstraints: isCa(false)
                       critical(false) 2.5.29.35 value = Sequence
    Tagged [0] IMPLICIT 
        DER Octet String[20] 

                       critical(true) KeyUsage: 0xa8
                       critical(false) 2.5.29.17 value = Sequence
    Tagged [1] IMPLICIT 
        DER Octet String[16] 
    Tagged [2] IMPLICIT 
        DER Octet String[16] 
    Tagged [2] IMPLICIT 
        DER Octet String[20] 

                       critical(false) 2.5.29.14 value = DER

What is wrong with my setup?

2 Answers

Voted

garethTheRed · Answer 1 · 2021-11-12T23:36:47+08:00

Best Answer

garethTheRed

2021-11-12T23:36:47+08:002021-11-12T23:36:47+08:00

There are two issues with the certificates posted in the question:

Both certificates are using one shared key. As a certificate should bind a key to its owner (Subject) it really doesn't make sense to use one key for two subjects.
As a consequence of the above, the Subject Key Identifier and Authority Key Identifier hashes are the same across both certificates.

Note that you also have a rather complex Authority Key Identifier in the end-entity certificate. It is usual to just have the hash in here, copied directly from the Subject Key Identifier of the issuing CA's certificate. That is, leave out the Directory and Serial entries. What you have may work, but why risk it?

1

Justa Guy · Answer 2 · 2021-11-25T08:56:47+08:00

Justa Guy

2021-11-25T08:56:47+08:002021-11-25T08:56:47+08:00

A certificate signed by your own fictitious certificate authority will always throw errors because the CA isn't trusted by your system. To get the green lock you have to add your certificate authority's self-signed certificate to the trusted root certification authorities store on the machine.

Even if you trust your fictitious CA on your own machine the certificate that was signed by this CA won't be trusted by other machines on the internet. If you want your certificate to be trusted by other machines you must pay a legitimate certificate authority to have them sign your certificate for you.

If your CA is already installed properly in trusted root CAs and your actual key length is 1024 it may be too weak to be trusted. Try regenerating it with at least 2048 length since every now and then browsers deprecate the shorter key lengths.

0

NET::ERR_CERT_AUTHORITY_INVALID with self-signed CA in Windows

Key and Certificate:

CA Summary

Server Certificate

Cert Summary

Can you pass user/pass for HTTP Basic Authentication in URL parameters?

Ping a Specific Port

Check if port is open or closed on a Linux server?

How to automate SSH login with password?

How do I tell Git for Windows where to find my private RSA key?

What's the default superuser username/password for postgres after a new install?

What port does SFTP use?

Command line to list users in a Windows Active Directory group?

What is a Pem file and how does it differ from other OpenSSL Generated Key File Formats?

How to determine if a bash variable is empty?