http://www.bbc.com/news/technology-40366823
Dead man's switch?
32TB of Windows 10 internal builds, core source code leak online
21–30 of 94 posts
Re: 32TB of Windows 10 internal builds, core source code leak online
#22Throwaway account for obvious reasons. Does anyone have a link to the leaked data?
At this point avoiding links is pointless as the source code will be essentially public knowledge in matter of days/weeks. Damage control is the only strategy left. The sooner security researchers outside Microsoft can start analyzing and reporting vulnerabilities, the better.
Re: 32TB of Windows 10 internal builds, core source code leak online
#23Looks like the WINE developers are going to have the time of their lives.
It looks like mainly kernel and drivers were leaked. WINE is emulating the Win32, which is distinct from the Windows NT kernel & drivers - kind of like how the Linux API is distinct from the Windows NT kernel, despite Windows supporting it. This might be a boon for the ReactOS folks, who are trying to implement the NT kernel, except for seeing the Windows source code automatically disqualifies you from being a contri…
Exactly. A few years ago the ReactOS developers had to stop all development for several months to perform a source code audit. This was meant to deflect accusations that they had derived code from disassembled Windows binaries.
If anything, this could make their legal situation more sticky.
Re: 32TB of Windows 10 internal builds, core source code leak online
#24Looks like there's some debate as to whether or not this has been exaggerated: https://www.betaarchive.com/forum/viewtopic.php?t=37282
So far I haven't seen any links to source code.
Quote from one of the admins:
> Yes I have no idea where they got the 32TB stuff. We had a big leak of Win10 builds yes, but these were all Windows Insider stuff that were collected over time available to all Windows Insider members at one time or another.
Edit: BA's official statement: https://www.betaarchive.com/forum/viewtopic.php?f=1&t=37283
Re: 32TB of Windows 10 internal builds, core source code leak online
#25Throwaway account for obvious reasons. Does anyone have a link to the leaked data? At this point avoiding links is pointless as the source code will be essentially public knowledge in matter of days/weeks. Damage control is the only strategy left. The sooner security researchers outside Microsoft can start analyzing and reporting vulnerabilities, the better.
Some of the leaked data seems to currently only be accessible on a https://www.betaarchive.com/ , but your account won't be able to access it for a month or so.
Re: 32TB of Windows 10 internal builds, core source code leak online
#26[deleted]
Re: 32TB of Windows 10 internal builds, core source code leak online
#27I must be possible to determine when this code was collected by matching the files to version control time stamps.
I wonder if that could be used to narrow down who pulled the code during that window.
Re: 32TB of Windows 10 internal builds, core source code leak online
#28I guess windows 10 is now open source!
Re: 32TB of Windows 10 internal builds, core source code leak online
#29Looks like the WINE developers are going to have the time of their lives.
Quite the opposite. WINE developers will have to go an extra mile to avoid getting anywhere even remotely close to the proprietary source code, otherwise they may get sued for copyright infringement -- even if they didn't intentionally copied any of the code.
Re: 32TB of Windows 10 internal builds, core source code leak online
#30This will make Windows less secure in the short term, but as good and bad actors find bugs and Microsoft patches them, they will end up with a hardened product. Their OS is now effectively open-source.
> Their OS is now effectively open-source.
Ehh, Panic software had a good post-mortem talking about this potentially happening to them https://panic.com/blog/stolen-source-code/
My favorite takeaway was, "With every day that passes, that stolen source code is more and more out-of-date."
I remember hearing Windows source code leaks in the past (I see articles from 2000 and 2004) and remember hearing about problems with "clean room" implementations of open source SMB implementations.
Yeah, the fundamentals and much of the source code will probably stick around for many, many years. But this has happened before and I don't see why this is any more of a big deal.