Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

theregister.co.uk

Post reply on HN
Print view View original

51–60 of 94 posts

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

#51

Post by gtirloni »

wfunction wrote: post #50
KGIII wrote: post #34

Earlier quoted context omitted.

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 Exp…

How do you "ask them"? Do they have an email address for this? Or do you have to find the right guy on the team somehow?

Windows Shared Source initiative has existed for what, over 10 years now?

https://www.microsoft.com/en-us/sharedsource/

I think this "leak" is greatly exhagerated.

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

#52

Post by Teever »

KGIII wrote: post #34
gpm wrote: post #32

Earlier quoted context omitted.

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 Exp…

Do they share the code for the windows update mechanisms and the code for cortana and other spyware that is installed by default in windows?

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

#53

Post by wfunction »

gtirloni wrote: post #51
wfunction wrote: post #50

Earlier quoted context omitted.

How do you "ask them"? Do they have an email address for this? Or do you have to find the right guy on the team somehow?

Windows Shared Source initiative has existed for what, over 10 years now? https://www.microsoft.com/en-us/sharedsource/ I think this "leak" is greatly exhagerated.

None of those categories seem to include ordinary developers though?

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

#54

Post by ryanlol »

diodesign wrote: post #47
driverdan wrote: post #24

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…

Hiya - I wrote the article. What's happened is that the Beta Archive folks have now deleted (or in the process of deleting) the private material that was uploaded to the BA FTP. There most definitely was non-officially-released internal Microsoft files in the archive, regardless of BA's intentions, such as the Shared Source Kit, the ARM64 Windows Server build, the Mobile Adaption Kit, and various prerelease versions…

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?

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

#55

Post by KGIII »

Teever wrote: post #52
KGIII wrote: post #34

Earlier quoted context omitted.

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 Exp…

Do they share the code for the windows update mechanisms and the code for cortana and other spyware that is installed by default in windows?

I have no idea. I haven't used Windows in a years. Give it a shot. The most they can do is tell you no.

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

#56

Post by KGIII »

wfunction wrote: post #53
gtirloni wrote: post #51

Earlier quoted context omitted.

Windows Shared Source initiative has existed for what, over 10 years now? https://www.microsoft.com/en-us/sharedsource/ I think this "leak" is greatly exhagerated.

None of those categories seem to include ordinary developers though?

If your company, or you, have a relationship with Microsoft, try the Enterprise. They are pretty lenient, though not always rapid in their responses.

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

#57

Post by diodesign »

ryanlol wrote: post #54
diodesign wrote: post #47

Earlier quoted context omitted.

Hiya - I wrote the article. What's happened is that the Beta Archive folks have now deleted (or in the process of deleting) the private material that was uploaded to the BA FTP. There most definitely was non-officially-released internal Microsoft files in the archive, regardless of BA's intentions, such as the Shared Source Kit, the ARM64 Windows Server build, the Mobile Adaption Kit, and various prerelease versions…

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.

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

#58

Post by wfunction »

KGIII wrote: post #56
wfunction wrote: post #53

Earlier quoted context omitted.

None of those categories seem to include ordinary developers though?

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

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

#59

Post by kabdib »

diodesign wrote: post #57
ryanlol wrote: post #54

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

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.

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

#60

Post by yjftsjthsd-h »

jcranmer wrote: post #49
43224gg252 wrote: post #43

Earlier quoted context omitted.

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.

> 1. How would Microsoft prove that they saw the code? Get the court to order discovery on all of your computers. They could probably also get subpoenas for the source code hosting sites to reveal relevant access logs. Or someone could admit to reading the source code someplace public, like a bug tracker. Or they could argue that the choice of variable names and minor details of algorithm details are too close to be…

> you'd have to think the FSF looks bad for suing people for violating the GPL

I agree with your, but there are people who argue this.

Post reply on HN