# How standard libraries read PEM files

1 PEM file from loremfile.dev, given to 4 standard-library readers in 14 runtime versions: which read them, which refuse, which differ.

The page: <https://loremfile.dev/compat/pem>.

1 PEM file given to 4 readers in 14 runtime versions. Cells of the ordinary files: reads 14, differs 0, refuses 0, crashes 0.

| File | Manifest says | go/crypto/x509 | java/java.security.cert.CertificateFactory | node/crypto.X509Certificate | ruby/OpenSSL::X509::Certificate | Python (no reader) |
|---|---|---|---|---|---|---|
| [`pem/self-signed-ed25519-cert.pem`](https://loremfile.dev/pem/self-signed-ed25519-cert.pem) (542 B) | dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example | **reads** reports dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example | **reads** reports dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example | **reads** reports dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example | **reads** reports dns_names [fixture.example], issuer_cn fixture.example, serial 1409983142208024964197, subject_cn fixture.example | **no-reader** |

Python has no reader for these files. The standard library has no certificate parser: ssl loads certificates for TLS and offers none that returns a subject, an issuer, a serial and names.

The results as JSON: <https://github.com/kumarprabhashanand/loremfile/blob/main/compat/results/pem.json>.
