dogear

enter for all results · esc to close

JOSE is a Bad Standard That Everyone Should Avoid

paragonie.comsite

The standards are either completely broken or complex minefields hard to navigate.

visit paragonie.com ↗
0
sign in to dogear this
from
IAM
added
2026-10-10
likes
0

similar

  1. JOSE github.com
    tool category #cl link ↗
  2. SAML: A Fractal of Bad Design blog.trailofbits.com
    site category #iam link ↗

    “SAML is being crushed under the weight of its own complexity.” The author lists five flaws that compound: “1. Built on XML; 2. Canonicalization; 3. Enveloped signatures; 4. 'Kitchen-sink' design; 5. Ossification.” So instead of one more mitigation, identity providers get a…

  3. go-jose github.com
    tool category #go link ↗

    Fairly complete implementation of the JOSE working group's JSON Web Token, JSON Web Signatures, and JSON Web Encryption specs.

  4. IAM is hard. It's really hard. web.archive.org
    site category #iam link ↗

    “Overly permissive AWS IAM policies that allowed s3:GetObject to * (all) resources”, led to $80 million fine for Capital One. The only reason why you can't overlook IAM as a business owner.

  5. jio github.com
    tool category #go link ↗

    jio is a json schema validator similar to joi.

  6. Magento Coding Standards github.com
    tool category #magento2 link ↗

    🫡 - Official Magento 2 advanced ruleset for PHP_CodeSniffer.

IAM › Password-less auth > JWT: “The standards are either completely broken or complex minefields hard to navigate.”