---
answer: direct
beat: dev-practices
source: 1 article · updated: November 17, 2026
---

How does PASETO structurally prevent the 'alg:none' style of attack?

PASETO tokens declare a version and purpose (like 'v4.local' or 'v4.public') that map to one fixed, predetermined cryptographic recipe — there's no algorithm field to manipulate, because there's no algorithm choice exposed to the token at all. A 'v4.public' token is always verified with the same fixed asymmetric signing scheme; there's no code path where an attacker can supply a different, weaker algorithm for the verifier to honor.

Answered in

JWT's Real Problem Was Never the Idea, It Was the Choices It Allows

JWT 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.

Crashtech Editorial November 17, 2026 Development Best Practices

Read the full analysis

Other questions this article answers

More development best practices questions

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.