Twitter | Pretraživanje | |
koto
security ninja wannabe
5.227
Tweetovi
384
Pratim
8.391
Osobe koje vas prate
Tweetovi
koto 2. velj
Odgovor korisniku/ci @SecurityMB
Gratulacje!!!
Reply Retweet Označi sa "sviđa mi se"
koto 31. sij
Congratulations!
Reply Retweet Označi sa "sviđa mi se"
koto 29. sij
Odgovor korisniku/ci @skeptic_fx @mikispag i 3 ostali
You may be able to tighten the unsafe-eval with trusted types.
Reply Retweet Označi sa "sviđa mi se"
koto 29. sij
Odgovor korisniku/ci @mattaustin @kravietz_
I can understand the snarkiness, but still - AMP has tons of existing customers,and those will still be exposed to CSRF. Brushing that off only to take a stab at AMP is a position that's... not very helpful.
Reply Retweet Označi sa "sviđa mi se"
koto 28. sij
Odgovor korisniku/ci @kravietz_
I'm guessing AMP websites might want to have a say.
Reply Retweet Označi sa "sviđa mi se"
koto 28. sij
In other words, some AMP pages will have to opt out of the mechanism that addresses CSRF so cleanly. Sad.
Reply Retweet Označi sa "sviđa mi se"
koto proslijedio/la je tweet
Phineas 27. sij
Remember, Marcus Aurelius has already absolved you of the duty of having a take
Reply Retweet Označi sa "sviđa mi se"
koto 25. sij
Odgovor korisniku/ci @arkadiyt @frgx
Parts of CSP we could definitely do without. Some forms of it increase deployment complexity without significant enough value. See
Reply Retweet Označi sa "sviđa mi se"
koto 24. sij
Odgovor korisniku/ci @epereiralopez
Welcome to the team!
Reply Retweet Označi sa "sviđa mi se"
koto 24. sij
There's some nuance to this, but, without splitting hairs, the best advice for the end users in response to the paper is indeed NOT to disable ITP.
Reply Retweet Označi sa "sviđa mi se"
koto proslijedio/la je tweet
Kelsey Hightower 23. sij
When your decision to adopt microservices is missing the big picture.
Reply Retweet Označi sa "sviđa mi se"
koto 22. sij
Odgovor korisniku/ci @arturjanc @empijei @we1x
In terms of technical details, has a good summary.
Reply Retweet Označi sa "sviđa mi se"
koto proslijedio/la je tweet
Artur Janc 22. sij
Earlier today we published the details of a set of vulnerabilities in Safari's Intelligent Tracking Prevention privacy mechanism: . They are... interesting. [1/9]
Reply Retweet Označi sa "sviđa mi se"
koto 22. sij
The time has come to fix that typo in Referer ;)
Reply Retweet Označi sa "sviđa mi se"
koto 22. sij
Our title is boring, 's "Preventing Tracking Prevention Tracking" is way better ;)
Reply Retweet Označi sa "sviđa mi se"
koto proslijedio/la je tweet
Ben Stock 16. sij
Have an idea that would totally change the Web's security but would break today's Web? We have the right workshop for you! &I are hosting , *the* place for those ideas. We also have a keynote from the Web's chief deprecator
Reply Retweet Označi sa "sviđa mi se"
koto 15. sij
Odgovor korisniku/ci @KingstonTime
Oh man, that's terrible :( Hope something new, and greater will come out of this! Sending lots of <3. We are hiring as well for multiple roles, if you're interested.
Reply Retweet Označi sa "sviđa mi se"
koto proslijedio/la je tweet
Brad Hill 15. sij
💕❤️💕 for all who have worked for a better web and a better world at Mozilla.
Reply Retweet Označi sa "sviđa mi se"
koto 15. sij
Odgovor korisniku/ci @KingstonTime
Wait what? Is that for real?
Reply Retweet Označi sa "sviđa mi se"
koto 14. sij
Odgovor korisniku/ci @arkenoi @ivanristic
So was XHR ;)
Reply Retweet Označi sa "sviđa mi se"