If you're coordinating disclosure, you're supposed to *understand* the interactions between different bits of software, and encourage cross-vendor collaboration to make the impact known and figure out how mitigations are deployed and interact. The researchers totally botched this
-
-
Replying to @marcan42 @matthew_d_green
The fact that *I* needed to go around asking some people for info and digging for commits and bugs and mailing list threads to figure out how the fuck this all works and that nobody else did so tells me this disclosure was a massive clusterfuck, and that's on the researchers.
1 reply 0 retweets 0 likes -
Replying to @marcan42
The researchers notified every single relevant project. What precisely are you asking them to do differently? They gave months of notice on a handful of bugs with a SIMPLE PATCH.
2 replies 0 retweets 0 likes -
Replying to @matthew_d_green
*Follow up* on that notice to actually find out what got patched where. Because when I asked *them* they still claimed Thunderbird was vulnerable (to the PGP issue, in context) which turned out to be total bullshit.
1 reply 0 retweets 0 likes -
Replying to @marcan42
Thunderbird kept their ticket private. I don’t think the researchers (and the CERT) were told the status.
1 reply 0 retweets 0 likes -
Replying to @matthew_d_green
So.... ask? Or, you know, just *try* the damn exploit on the current release (like I did) before coordinating a panic-inducing media reaction with the EFF?
1 reply 0 retweets 0 likes -
Replying to @marcan42
The panic inducing media reaction that led to the advice to “temporarily disable PGP clients”, some of which turned out to be still vulnerable (albeit on unlikely cipher choices)? Hardly seems a big deal. The pro-PGP community has invented an overreaction where none exists.
1 reply 0 retweets 1 like -
Replying to @matthew_d_green @marcan42
Then they invented a disclosure problem where none existed.
1 reply 0 retweets 2 likes -
Replying to @matthew_d_green @marcan42
Literally every single early reaction by the community has turned out to be false or disingenuous. And now we’re literally scraping the ocean bed for new reasons to blame the researchers.
1 reply 0 retweets 3 likes -
Replying to @matthew_d_green
You're entitled to your opinion. I think the disclosure here was a shining example of how *not* to do things. We need a much higher bar than this. Lack of version numbers, pointless censorship of vendor names forbidding collaboration, no follow-up on patches whatsoever, etc
2 replies 0 retweets 1 like
I mean, seriously, there isn't a simple table of affected vs fixed versions anywhere. The Efail website is basically "all these vendors are affected and maybe they'll fix it, maybe they won't, maybe they'll miss something, we dunno just be scared ¯\_(ツ)_/¯"
-
-
Replying to @marcan42
Good. Being scared was the right reaction! If it meant people didn’t check their email for a day or so until Enigmail et al. got their disclosure/patch story straight!
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.