Me: I should improve the Content Security Policy settings on my admin domain
/me pokes load logging display
Me: Huh, looks like it'll be easier to allow some hashes this time. Might get a bit chunky as a header, but it's only me using it occasionally. But also, JQuery is adding CSS, so I need `strict-dynamic` to pass on trust
CSP: Strict Dynamic means that `self` no longer works and lots of other things have now broken as well.
Me: Bugger.
/me checks what else is in the admin area
Me: Ah. phpMyAdmin. Didn't think of that. That's going to be MUCH worse. Given how they're a major attack surface, I wonder whether they're CSP-compliant yet…
/me finds a Stack Overflow question asking about phpMyAdmin and CSP
Me: How bad could it be?
Asker: What's a CSP value that is secure but allows phpMyAdmin to run?
Only answer (from 2019): Have you tried `unsafe-inline` _and_ `unsafe-eval`?
Me: 😱