Spotting base64 encoded JSON, certificates, and private keys
11–20 of 135 posts
Re: Spotting base64 encoded JSON, certificates, and private keys
#12I don't really love this. It just feels so wasteful. JWT does it as well. Even in this example, they are double base64 encoding strings (the salt). It's really too bad that there's really nothing quite like json. Everything speaks it and can write it. It'd be nice if something like protobuf was easier to write and read in a schemeless fashion.
Re: Spotting base64 encoded JSON, certificates, and private keys
#13Re: Spotting base64 encoded JSON, certificates, and private keys
#14The 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?)
You can't spot private keys, unless they start with a repeating text sequence (or use the PEM format with header also encoded).
Re: Spotting base64 encoded JSON, certificates, and private keys
#15Isn't this obvious to anyone who has seen a few base64 encoded json strings or certificates? ey and LS are a staple.
Re: Spotting base64 encoded JSON, certificates, and private keys
#16I built a JWT support library at work ( https://github.com/geldata/gel-rust/tree/master/gel-jwt ) and I can confirm that JWTs all sound like "eyyyyyy" in my head.
Re: Spotting base64 encoded JSON, certificates, and private keys
#17Re: Spotting base64 encoded JSON, certificates, and private keys
#18Isn't this obvious to anyone who has seen a few base64 encoded json strings or certificates? ey and LS are a staple.
Re: Spotting base64 encoded JSON, certificates, and private keys
#19Isn't this obvious to anyone who has seen a few base64 encoded json strings or certificates? ey and LS are a staple.