Which brings us back to question why NSA didn't warn at least major providers, like MSFT, when SB threatened to leak these tools.
-
-
Replying to @emptywheel @hackerfantastic
That's a fair question, though I'm not sure I'd automatically presume there hasn't been prior disclosure.
2 replies 0 retweets 5 likes -
it's a good question but the answer nobody wants to acknowledge is that the NSA didn't know which vulns they needed to warn about
1 reply 0 retweets 0 likes -
Not true in this case.
1 reply 0 retweets 0 likes -
Replying to @emptywheel @hackerfantastic
Has Microsoft confirmed no disclosure or is that just assumption b/c no patch? I'd believe no disclosure, just see it as unanswered for now.
1 reply 1 retweet 2 likes -
Replying to @Susan_Hennessey @hackerfantastic
I agree it's unanswered. I haven't called MSFT but others have gotten no details thus far.
2 replies 0 retweets 0 likes -
davi ((( 🐧))) 德海 Retweeted davi ((( 🐧))) 德海
warning on so many post-EOL systems is interesting twist. will MSFT try again to force upgrades on laggards?https://twitter.com/daviottenheimer/status/852979580054917121 …
davi ((( 🐧))) 德海 added,
1 reply 0 retweets 0 likes -
Replying to @daviottenheimer @emptywheel and
even with notice really speaks to warning int'l targets more than domestic. abroad upgrade/patch cycles far slower or non-existentpic.twitter.com/ZNFCcYS3oU
1 reply 0 retweets 0 likes -
So has NSA decided it's not big deal if MSFT loses market share because of this?
1 reply 0 retweets 0 likes -
hmm a bit like asking if MSFT decided it wants to lose market share by writing poor code and letting others profit from it
4 replies 0 retweets 0 likes
It has always worked so far.
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.