News for hackers. Stuff that matters.
Re:Synology Security Advisory by catlifeonmars on Friday November 20, 2026 @12:21AM (#50570483)
[delayed]
Re:Synology Security Advisory by Liuser on Friday November 20, 2026 @12:57AM (#50570690)
Yeah that I get, but I’m disputing that the tool (mTLS) is not at fault for being misused, authz (rather the lack of it) is being misused. The tool (authn) is working fine.
Re:Synology Security Advisory by cloudfudge on Friday November 20, 2026 @03:08AM (#50571592)
We are saying the same thing. mtls is fine for authn. But nobody actually uses it for just that. They use it for both authn and authz. The authz policy is almost always just "identity != null".

If I told you not to use a power drill as a hammer, you wouldn't claim I'm saying the hammer is at fault for being a bad power drill.

Re:Synology Security Advisory by catlifeonmars on Friday November 20, 2026 @03:40AM (#50571861)
[delayed]
Re:Synology Security Advisory by Liuser on Friday November 20, 2026 @08:51AM (#50574640)
Yes, this I agree with that. JWT is simpler to work with by virtue of remaining on http layer 7 and parsing claims out of JSON compared to working with extracting identity and other embeddings from x509.

I just take issue (maybe pedantically so) calling it a bad tool and blanket statements that no one uses it for just authn but for authz also. It’s not used for authz. The absence of authz shouldn’t be blamed on mTLS.