Live data from Hacker News

32TB of Windows 10 internal builds, core source code leak online

theregister.co.uk

31–40 of 94 posts

Re: 32TB of Windows 10 internal builds, core source code leak online

#31
post #6
post #5

This 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.

It's only some core kernel and driver code, lower than 1% of the codebase.

Yup. It's the Windows Shared Source Kit, which is already mostly public. Many of the big security firms and government agencies already have licences to the full source code anyway.

The only thing this really gains anyone is it possible some non-public debug symbols might have been left in some builds. Not earth shattering.

Re: 32TB of Windows 10 internal builds, core source code leak online

#32

Looks 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 o…

There does seem to be some source, as (now, not when you posted) discussed in that thread. Here's a pastebin (taken from that thread) with some filenames, including, for example, usb drivers

https://pastebin.com/raw/VGEbWVSM

Re: 32TB of Windows 10 internal builds, core source code leak online

#34
post #32

Looks 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 o…

There does seem to be some source, as (now, not when you posted) discussed in that thread. Here's a pastebin (taken from that thread) with some filenames, including, for example, usb drivers https://pastebin.com/raw/VGEbWVSM

If you really want to see some Windows source code. You can just ask them - and they will send it to you. It's not open source and there are limits to what you can do with it.

They call it their Shared Source Initiative. They want a reason for sharing it with you but I have used, 'I am just curious.' With that excuse, this was a long time ago when I still used Windows, I got the specific code I wanted for Outlook Express.

Re: 32TB of Windows 10 internal builds, core source code leak online

#36
post #12

Earlier quoted context omitted.

Microsoft actually provides symbols for most windows components through its symbol server.

The private symbols in these builds could actually be very useful. The article alluded there were private symbols. So, even if only 1% of the overall windows code was leaked, if there were, say private symbols for the heap allocator of the kernel, for a practiced reverse engineer that is pure gold. Not as good as code, but a hell of a lot better than having to figure everything out and name functions and symbols them…

What kinds of private symbols aren't served by the symbol server?

Re: 32TB of Windows 10 internal builds, core source code leak online

#40
post #35

Given the other article I read today about US companies bowing to Russian requirements to review source code, I wonder if MS has also already given away code that can be studied for security gaps.

Microsoft indeed make their sources available for review by major customers including governments. From what I heard this is done under NDA and reviewers are forbidden from taking the code away from MS facility.
Post reply on HN