Are you referring to the 'logging in to Gmail logs you into Chrome' behavior, or something different?
-
-
Replying to @Pinboard
Vítor Galvão Retweeted Christoph Tavan
That and not clearing the cookies for their own services: https://twitter.com/ctavan/status/1044282084020441088 … and at this point I’d even say I expect more stuff like this to surface (I think I’m forgetting one), hence the question.
Vítor Galvão added,
1 reply 0 retweets 0 likes -
Replying to @vhgalvao
The point of telling campaigns to use Chrome is to keep them safer from malware. Google tracking is not a problem or threat in the campaign context, so we'll continue to recommend the safest browser, which is currently Chrome.
2 replies 0 retweets 2 likes -
Firefox is fine if your threat model is malware. The sandboxes are comparable at this point.
2 replies 0 retweets 4 likes -
To wit: most of the sandbox is literally the same code.
1 reply 0 retweets 0 likes -
I wouldn't even imagine sandbox escapes are a real threat for most congressional campaigns. More like phishing (the Safebrowsing list is the same?) and known vulns (does Firefox autoupdate the same as Chrome?).
2 replies 0 retweets 0 likes -
Yes, Firefox auto-update is effectively the same as that of Chrome.
1 reply 0 retweets 0 likes -
Just 'cause I'm curious (and I don't think CA ecosystem attacks are really in-scope, either), what's the comparison of Firefox to Chrome with respect to various HTTPS enhancements (I see Firefox has CT support, deprecated SHA1 chains, etc). Got any handy references?
1 reply 0 retweets 0 likes -
I believe they’re comparable, but I’m not an expert here. See https://blog.mozilla.org/security/
1 reply 0 retweets 0 likes -
Yeah, I skimmed. It looked fairly comparable. *shrug* Like I said, I think the biggest threat is unpatched browsers and phishing.
@Pinboard is doing the Lord's work by distributing Security Keys.1 reply 0 retweets 0 likes
Strong agree on both counts. If you’re using a major browser, it doesn’t matter that much which one it is at this point.
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.