Domino on Linux/Unix, Troubleshooting, Best Practices, Tips and more ...

 
alt

Daniel Nashed

 

Certificate ASN.1 Decoding online

Daniel Nashed  14 February 2024 21:02:48

Now that I posted the TLS 1.2 interactive information side today, some of you might also want to get details out of certificates.

Certificates are usually public information. So it should be OK to paste them into the website https://asn1js.eu/.
But there is a GitHub project referenced and you could run it also locally.

The inner guts of certificates are presented in ASN.1. When you ever has looked at OpenSSL C code, you will recognize the structures.

The interactive parser can be quite helpful if you ever need to leave the normal path working with OpenSSL command line converting certs between PEM, DER, PKCS12 and other formats.

The ASN.1 form is basically what you get when you convert to DER. It's a binary format fun to read. But usually you don't have to look at it. The normal OpenSSL code and other security libs hide most of the complexity.

On the website you also find some examples of certificates you can load.

-- Daniel


Image:ASN.1 Decoding online


Comments

1Error when importing personal SMIME Certificate  16.02.2024 10:32:42  Certificate ASN.1 Decoding online

As a side note:

We as an organization (had) to change our provider for individual S/MIME certificates recently.

These individual certificates are now provided from the company named Sectigo (see: https://www.sectigo.com/).

When trying to import a newly provided certificate into the Notes/Domino ID file, we ran into the following error from the Notes client:

Wrong ASN.1 type.

Cannot add certificate from the import file.

After some time, we found a solution:

One has to first import the key in Firefox and then export it immediately after. Now you can import the key into the Notes ID using the Notes client (here 12.0.2FP2).

Strange - but a feasible workaround in our case.

Know you (also) know ;-)

Regards,

Uwe

2Daniel Nashed  18.02.2024 12:09:20  Certificate ASN.1 Decoding online

@Uwe, as explained in a private mail, you should provide this type of information to HCL to look into it.

If this is PEM format, you would be able to just provide the certificate data.

The certificate content should not change if imported and exported again.

But it could be that a certificate contains invalid data, which is ignored by Firefox and when exported it works.

I would always double check with OpenSSL as a reference.

You can for example use openssl asn1parse --> https://www.openssl.org/docs/manmaster/man1/openssl-asn1parse.html

It's hard to tell without having a file to look at. If you could get test certificate that is the same type of certificate and shows the same problem, please open a ticket and get it escalated to the security team.

You can also send it to me to have a look .. We can also look at it together in your environment.

--Daniel

Links

    Archives


    • [HCL Domino]
    • [Domino on Linux]
    • [Nash!Com]
    • [Daniel Nashed]