is ng-csp detrimental to user security?
-
-
Yes, the Angular security model based on bypassing platform security features (via {{ }} and AST*) is wrong
2 replies 0 retweets 1 like -
OK, and how would you have done ng-csp differently?
1 reply 0 retweets 0 likes -
I'll bite: if your JS FW bypasses platform restrictions you either fail closed or reimplement them yourself.
1 reply 0 retweets 0 likes -
Replying to @arturjanc @sirdarckcat and
So for Angular, just don't implement ASTInterpreter or require nonces/hashes for expressions.
1 reply 0 retweets 0 likes -
If they hadn't implemented it, authors wouldn't have been able to use CSP. How is this different?
1 reply 0 retweets 0 likes -
Replying to @sirdarckcat @arturjanc and
I don't think ng-csp did any "harm" to users. On the contrary, it allowed authors to adopt (a version of) CSP.
3 replies 0 retweets 0 likes -
Yeah, and this mentality of bypassing security mechanisms also gave us template injections.
1 reply 0 retweets 0 likes -
What? That makes no sense :-). Template Injections existed before ng-csp.
1 reply 0 retweets 0 likes -
It's just an example of how the approach of "let's make it work despite security restrictions" is harmful.
2 replies 0 retweets 0 likes
Which brings us back to the point that bypassing security for "convenience" is an anti-pattern and must die.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.