It seems that the "leak" was what you need to develop a driver. You can sign up for MSDN and get that, right? Does that come with the $3000/year it now costs to subscribe to MSDN?
32TB of Windows 10 internal builds, core source code leak online
61–70 of 94 posts
Re: 32TB of Windows 10 internal builds, core source code leak online
#62Earlier quoted context omitted.
Clarify the 32TB and 8TB figures please. People with access to the archive who successfully downloaded the confidential stuff did not get nearly that much. Do you consider windows installation images to be "compressed files" in this context?
Compressed, it is ~8TB. Fully expanded it is ~32TB. I think the bigger issue is not the final size, but that internal Microsoft material - particularly source code - has escaped into public FTP. That, to me, is the main thing, right? C.
>Compressed, it is ~8TB.
But what data does this 8TB refer to specifically? Is this the source + all the windows builds from a plethora of sources? Did you download 8TB of data from BA and expand it to 32TB or was this a figure provided to you by one of the raided hackers or their associates?
>think the bigger issue is not the final size, but that internal Microsoft material - particularly source code - has escaped into public FTP
Happens regularly, although usually it's MS employees leaving stuff in public FTPs or inside released ISOs, updates, whatever. redmond\ domain is huge and the (accidental or not) leaks never stop.
Re: 32TB of Windows 10 internal builds, core source code leak online
#63Earlier quoted context omitted.
Compressed, it is ~8TB. Fully expanded it is ~32TB. I think the bigger issue is not the final size, but that internal Microsoft material - particularly source code - has escaped into public FTP. That, to me, is the main thing, right? C.
Windows sources have escaped before. I doubt that Windows is buildable outside of Microsoft (and the bits are definitely not signable, since you need access to a key vault for that). Useful for research, and finding security issues. Not much else.
Might be helpful to the reactos and wine folks if unofficially.
Re: 32TB of Windows 10 internal builds, core source code leak online
#64Earlier quoted context omitted.
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.
> A few years ago the ReactOS developers had to stop all development for several months to perform a source code audit.
What kind of an audit can you do without access to the original software's source code? How would you tell if it's actually different?
Re: 32TB of Windows 10 internal builds, core source code leak online
#65This is a gross exaggeration. As far as I can see, what "leaked" was the "shared driver source kit" that nearly any hardware vendor (like chipset manufacturer) can get; basically anyone who puts up a few thousand bucks and signs an NDA.
Re: 32TB of Windows 10 internal builds, core source code leak online
#66Earlier quoted context omitted.
If your company, or you, have a relationship with Microsoft, try the Enterprise. They are pretty lenient, though not always rapid in their responses.
But the point is you need to already have a relationship, right? It seems you can't just say "I'm curious" (or even better, "I want to track down X bug") and expect to get source access, contrary to what was claimed earlier... Enterprise specifically says you need to "Maintain 10,000 Windows seats" which is not something a lone developer would do...
My only tie was having an MSDN subscription.
Re: 32TB of Windows 10 internal builds, core source code leak online
#67Earlier quoted context omitted.
Windows sources have escaped before. I doubt that Windows is buildable outside of Microsoft (and the bits are definitely not signable, since you need access to a key vault for that). Useful for research, and finding security issues. Not much else.
Might be helpful to the reactos and wine folks if unofficially.
Actually the opposite. They can't work in the project of they've seen the actual MS code even if they write their own code.
Re: 32TB of Windows 10 internal builds, core source code leak online
#68Links or it didn't happen.
Re: 32TB of Windows 10 internal builds, core source code leak online
#69Earlier quoted context omitted.
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.
1. How would Microsoft prove that they saw the code? 2. If microsoft sued wine devs it would be horrible for Microsofts public image. They won't do it. 3. I hope the WINE devs don't listen to you.
Holy hell do you remember SCO v. everyone?
Re: 32TB of Windows 10 internal builds, core source code leak online
#70Earlier quoted context omitted.
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.
That's unfortunate and doesn't fit my understanding of the situation - is disassembling a binary not fair game, in the same way that Samsung buying an iPhone and cracking it open is? (Assuming we're worried about copyright and not patents).