TIL that You can spot base64 encoded JSON, certificates, and private keys

Re:TIL that You can spot base64 encoded JSON, certificates, ... by mschuster91 on Wednesday August 06, 2025 @03:13AM (#44808704)

> The PEM format (that begins with `-----BEGIN [CERTIFICATE|CERTIFICATE REQUEST|PRIVATE KEY|X509 CRL|PUBLIC KEY]-----`) is already Base64 within the body.. the header and footer are ASCII, and shouldn't be encoded[0] (there's no link to the claim so perhaps there's another format similar to PEM?)

In practice, you will spot fully b64 encoded PEMs all the time once you have Kubernetes in play... create a Secret from a file and that's what you will find.

[ Parent | on HN ]

Re:TIL that You can spot base64 encoded JSON, certificates, ... by CBLT on Wednesday August 06, 2025 @09:10AM (#44811496)

I don't always store my Kubernetes Secrets in files, but when I do, I prefer stringData.

[ Parent | on HN ]

Re:TIL that You can spot base64 encoded JSON, certificates, ... by mdaniel on Wednesday August 06, 2025 @10:46AM (#44812741)

I believe OP meant $(kubectl get secret) which by default returns them in JSON and base64 encoded. I do agree with you that it would be stellar if kubectl were bright enough to recognize "there's no weird characters, show me in stringData" but there are already other way more important DX issues that haven't gotten any traction

[ Parent | on HN ]