@adamshostack@infosec.exchange
Post #3898438
2026-07-17 23:58 UTC
Replies (4)
-
@cjwatson@mastodon.ie 2026-07-18 00:52
@adamshostack@infosec.exchange Conceivably https://bugzilla.mozilla.org/show_bug.cgi?id=1473933 / https://github.com/mozilla-firefox/firefox/commit/6fa8cead8c202eea4eb0a490fa97edd29616919f? Would also need to check that there wasn't some other version of the delay after that change though - that's a bit too much git archaeology to do from my phone.
-
@octothorpe@mastodon.online 2026-07-18 01:24
@adamshostack@infosec.exchange @catsalad@infosec.exchange I don’t have an answer but now I’m super curious as to why the delay was there. To try and make people actually read the warning (ex: this extension can read all your shit), or some other technical one?
-
@sj@social.scriptjunkie.us 2026-07-18 02:09
@adamshostack@infosec.exchange clickjacking I'd presume
-
@lmk@infosec.exchange 2026-07-18 01:54
@adamshostack@infosec.exchange If only they had a threat model and we could see how they updated it. :-/