6 ms·

JWT with RSA or Ed25519 is definitely not a bad idea there.

• lvh 10y ago
  JWT does not define Ed25519 as part of the spec. It is supported "off-label" in one JWT library I could find (Joken) for a relatively uncommon language (Elixir). Frustratingly, JWT defines a tons of stuff, where few are required but some are "Recommended" and some are "Recommended+". I'm not sure what "Recommended+" means, but apparently it means "has known cryptographic flaws", because RSA with PKCSv15 padding is "Recommended+".
  • tscs37 10y ago
    I kinda went over the standard on that. The Go library I use allows to define custom algorithms, so I just set alg to ED2 and use it. It's within the app only so it doesn't hurt much. Also agree, it's rather frustrating that JWT is so well defined but something as simple as using Ed25519 is not part of the standard yet.
    • lvh 10y ago
      Out of interest, if you're going to go off-standard, why not just use libsodium and get decent crypto?
      • tscs37 10y ago
        Lazy I guess. The JWT Lib does most of the work and I just stuff in the Ed keys on both ends, don't need to do anything beyond that.
  • buckhx 10y ago
    ES256 is in the spec at least
    • CiPHPerCoder 10y ago
      The last thing the Internet needs more of is foot-bullety ECDSA deployed at scale. Point of order: Does ES256 enforce RFC 6979? If not, how do you know you aren't repeating k-values? The only sane crypto in the JWT specification is, sadly, HMAC.
  • arnarbi 10y ago
    Here's a draft: https://tools.ietf.org/html/draft-ietf-jose-cfrg-curves-06 https://tools.ietf.org/html/draft-ietf-jose-cfrg-curves-06