Is it just me or has this story changed at least twice since it broke? First the hacker had potentially had access to all sorts of source code for five weeks, then he had access to a little bit for only a couple of weeks, and now in this ZDNet story they're basically saying 'We knew the whole time, we were just testing.'
Of course, after twelve days of knowing there was an intruder and watching that intruder, Microsoft apparently still doesn't know who they are or where they're geographically located. Additionally, as a consultant in the article points out, one easily detected hacker "shouldn't have necessitated urgent calls to the FBI and a shutdown of all remote access for Microsoft's roughly 39,000 full-time employees world-wide." An excellent point.
Who knows if we'll ever find out the full extent of the breach (it's questionable as to whether the big MS even knows at this point) but it sounds as though the truth is somewhere between the original, high-level, months-long security breach, and the low-level "knew it all along" twelve day version.
|Aerocool starts Project 7 with a flurry of case and cooling gear||3|
|NTFS filesystem bug could crash Windows 7, 8, and 8.1||7|
|Enermax NeoChanger is both a pump and a reservoir||3|
|Acer sprinkles the Iconia Tab 10 with quantum dots||6|
|Deals of the week: lots of motherboards and a cheap GTX 1080||18|
|MSI Vortex G25VR, Infinite-A, and Pro 20EX PCs fill all niches||1|
|Nvidia unveils the GeForce GTX Battlebox certification program||25|
|Acer Spin 1 and Nitro 5 laptops are ready for school season||13|
|Ryzen AGESA 126.96.36.199 exposes more memory overclocking options||55|