What's the difference between PASETO's 'local' and 'public' token types?
Local PASETO tokens are symmetrically encrypted — the same key both creates and verifies them, and the payload is confidential, unreadable without that key. Public PASETO tokens are asymmetrically signed — verified with a public key, so anyone holding it can confirm authenticity and read the payload, but only the private key holder could have created it. The choice mirrors a real design decision: local tokens for confidentiality, public tokens for verifiable authenticity across multiple readers.
Answered in
JWT's Real Problem Was Never the Idea, It Was the Choices It AllowsJWT lets you choose 'none' as a signing algorithm. PASETO doesn't let you choose at all — versioned, fixed cipher suites instead of a menu of footguns.
Read the full analysisOther questions this article answers
- What's the actual security flaw people mean when they say JWT is risky?
- How does PASETO structurally prevent the 'alg:none' style of attack?
- If JWT's flaws are implementation choices, why not just implement JWT carefully instead of switching to PASETO?
- Does switching from JWT to PASETO fix authentication vulnerabilities unrelated to the token format itself?
More development best practices questions
- How many repositories can be scanned at once?
- Is GitHub AI Scan generally available?
- Can a developer continue any Copilot session on a phone?
- Does GitHub Mobile replace the desktop development environment?
- What should teams do when a Copilot model is retired?
- Does changing the model guarantee identical output?
- What's the actual security flaw people mean when they say JWT is risky?
- How does PASETO structurally prevent the 'alg:none' style of attack?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.