It's almost like Microsoft had a busy month because someone dropped a whole bunch of 0day local privesc bugs that soaked up a bunch of resources or something.https://twitter.com/taviso/status/1138632230111080448 …
-
Show this thread
-
Honestly I don't think this latest fulldisc drama involving
@taviso and Microsoft is one to get particularly emotional about. One of P0's objectives is to pressure vendors to up headcount so they can adequately resource responses to disclosures. Doubt any harm will come from this3 replies 0 retweets 18 likesShow this thread -
Replying to @riskybusiness
I'm used to it, we've had to fight hard to get this far
2 replies 0 retweets 6 likes -
Replying to @taviso
I'm a bit sympathetic to Microsoft on this one because of the month they've had patching all those locals. And to spot problems in regression testing just before release? That's shitty luck. Still, not the end of the world.
1 reply 0 retweets 1 like -
Replying to @riskybusiness
I have sympathy, but that's what the *three month* embargo is for, development and regression testing. Three months is beyond reasonable for something this, we would like to see this reduced.
2 replies 0 retweets 5 likes -
Replying to @taviso
Sure, I get your point of view. Just pointing out they had some unexpected shit drop in their laps with all the sandboxescaper stuff and wound up stretched a bit thin. Had that not have happened my feeling is they would have made the deadline.
4 replies 0 retweets 5 likes
I don't know that it's related, but if that's the case it's a useful data point that just one researcher can bring MSRC to their knees.
-
-
Replying to @taviso @riskybusiness
I had some sympathy with MS for the same reason Pat mentioned, but it’s hard to fault the logic of this comment :)
0 replies 0 retweets 0 likesThanks. 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.