Re:SAML: A Technical Primer
by bitexploder on Friday September 27, 2024 @06:20PM
(#41676098)
Lol, yeah, having SAML means putting XML parsing into critical security points. No thanks.
[ Parent
| on HN ]
Re:SAML: A Technical Primer
by poincaredisk on Friday September 27, 2024 @06:37PM
(#41676212)
Is it that different from parsing JSON? A honest question, what's the difference? Billion laughs attacks and similar?
It's not just XML formatting; it's bizarro stuff like XML canonicalization and comments, and it's in a signature format. It really might be the worst mainstream cryptosystem in the entire industry.
Re:SAML: A Technical Primer
by Jerrrrrrry on Friday September 27, 2024 @07:32PM
(#41676566)
A computer scientist would say they have identical parsing complexity, so not much.
A computer programmer wouldn't even know where to begin, as the chesterton's fence had long been rejustified
Re:SAML: A Technical Primer
by bitexploder on Saturday September 28, 2024 @01:26PM
(#41681643)
But it’s not true in practice. Pure simple XML vs JSON sure. XML you deal with in SAML has tons of extra things like namespaces, canonicalization issues, etc. it is way more complex and has led to many security issues over the years.
Re:SAML: A Technical Primer
by Jerrrrrrry on Saturday September 28, 2024 @07:09PM
(#41683552)
I had originally quoted
"in theory, it's easy in practice. in practice, its easy in theory"
But I thought scientist vs. programmer would be literally analogous and rivet more finches.
Re:SAML: A Technical Primer
by bitexploder on Friday September 27, 2024 @07:09PM
(#41676433)
Yeah, see the other replies in here. It is just a mess of ancient cruft and unclear implementation guidelines.
Even better: XML signatures, which are very easy to get wrong in both signing and verification.
Re:SAML: A Technical Primer
by bitexploder on Friday September 27, 2024 @07:07PM
(#41676424)
Yeah, it is a gross morass of pain and cruft and unclear implementation for devs.