W10 source code leaked

source or didn't happen

>>61047843
The Register

>>61047823
ReactOS doesn't use leaked source code.

>>61047843
https://www.theregister.co.uk/2017/06/23/windows_10_leak/
I'm expecting a Norwegian to make an archive link for me

>>61047823
But ReactOS devs can't even look at these

>>61047843
>>61047823

>>61047823
if the reactos guys even consider taking a look at it and microsoft will sue the shit out of them

>>61047823
So wait, does this mean we could compile our own botnet free win10?

There's nothing of value in the leaks.

>>61047897
after you

>>61047823
>stock hardware drivers and arm onecore code
Literally nothing.

>>61047823
>32 fucking TB
The fuck?

>>61047823
>when you're on a H1B and find out that it's not enough to feed your family back in India
Wew.

>>61047950
Complete builds and debugging symbols.
There's no interesting code in there >>61047934

>>61047897
No.

>>61047823
>wifi stacks
Jesus christ. Better remove that wifi chip or you'll be getting exploited by random radio waves now.

>>61047934
>source for drivers for undocumented hardware
>nothing

>>61048019
>undocumented hardware

>>61048030
>pointless greentext

>>61048050
I was quoting you. That's what greentext is for.

>>61048059
No shit, and your quote was pointless. Again, pointless greentext.

>>61047888
>>61047868
>>61047853

are these idiots intellectually handicapped?

>>61048073
Consider explaining what kind of "undocumented hardware" Windows has drivers for.

>>61048083
Basically anything that doesn't have an open source Linux driver. Without documentation on how hardware functions, drivers can't be made. Now that source code for said undocumented hardware is leaked, people can write Linux drivers for it. This means that hardware that either only had closed source Linux drivers or had no Linux drivers can now be made to function on Linux

File: Mount stupid.jpg (24KB, 600x338px) Image search: [Google]

24KB, 600x338px

>>61048076
(You)

>hosted on betaarchive
Well good luck getting access to their private ftp.

>>61047853
They are targeting XP anyways.

>>61048155
I know. Either way, a Windows leak of any version will not boost progress of ReactOS.

>>61048076
They're legally handicaped

>>61048112
>anything that doesn't have an open source Linux driver

>source to the base Windows 10 hardware drivers plus Redmond's PnP code, its USB and Wi-Fi stacks, its storage drivers, and ARM-specific OneCore kernel code
This doesn't include third-party drivers. Only inbox drivers for basic shit like usb, hid, ahci, etc. All of which are very well documented.

>unreleased internal builds, some debugging symbols, and source code for base hardware drivers
Wow, it's nothing.

>>61047823
might be cool to some folk but shitty windows drivers mean little to me

Where is actual link to this archive where I can download it?

>>61048351
You need private ftp on beta archive
which is fairly difficult to get nowadays.
https://www.betaarchive.com/contributions.php

IS IT OVER? IS MICROSOFT FINISHED & BANKRUPT?

>>61047950
Microsoft posted a blog about their migration to git recently.
They have 1 giant git repo that includes every component of the Windows OS, so it has tens of thousands of branches, several million commits, and millions and millions and millions of files.

I think they said it took all day for them to run a git status before they optimized it for their needs.

So think of all of those artifacts + the builds and debugging info.

>>61047823
I thought the actual OS source was leaked. This is interesting, but disappointing.

>>61048495
Sadly, no.

>>61047823
>leaked
"leaked"

>>61048495
No, it's just subsystems and a few debug build which don't have pdb symbols stripped etc.

File: hmmmm.png (19KB, 605x177px) Image search: [Google]

19KB, 605x177px

>>61048381
>it will take 160 days to download the whole 8 TB archive
lMFAO

Leaks do not help any of the open source projects, they don't use source code or even binary code, they use documentation provided by someone who reverse engineered the original binary. Using source code or binary code directly is not legal and will get their project shut down

>>61048972
Only in "freedom" land. In Europa it's totally legal.

>>61048709
Yeah, it's over guys. It's just a shtick beta archive did so the entire world and their mothers rush to pay them

>>61048019
>undocumented hardware
BUILD THE WALL

>>61049183
That hardware came to this country in search of a better future, you can't just kick it out man.

>>61048972
you're such a fucking retard

File: 1490667214934.jpg (17KB, 460x423px) Image search: [Google]

17KB, 460x423px

>>61048972
how the fuck can MS or any other company definitively "prove" that the ReactOS devs saw the source code? If they literally cut-pasted from Windows source, then yeah, maybe that makes sense. But if they just read over it, get some answers, and then implement it in a similar manner, how can MS prove that they saw the source?

File: dogger.jpg (16KB, 326x326px) Image search: [Google]

16KB, 326x326px

>>61049722

perhaps that is the plan

they probably have some tendril of their botnet in their office somewhere. when it gets released, they will use it to pull a bunch of their data and sue them for IP theft. it doesn't matter if they are right or not, micro$oft is big enough to survive an expensive lawsuit even if they lose, and it would cripple their competitors

>>61049722
The commits come in pretty slow because the whole process of reversing the binary and then documenting it and then re-implementing the binary from documentation is very time consuming. If there were a sudden surge in commits with no explainable reason (no documentation to explain how they discovered things) then it would raise some red flags.

>>61049780
Yeah I figured so, but unless there is definite, concrete evidence of source code from Windows being lifted and reused in ReactOS, Microsoft couldn't really have much of a case, right?

At any rate, ReactOS has a lot of activity in places like Russia. They probably don't give a single shit about MSFT. I'd imagine have no power if this leak is an actual happening

File: gnu+linux_facepalm.jpg (32KB, 572x184px) Image search: [Google]

32KB, 572x184px

But it's not open source so nobody's allowed to fix it.

>>61049821
>Yeah I figured so, but unless there is definite, concrete evidence of source code from Windows being lifted and reused in ReactOS, Microsoft couldn't really have much of a case, right?

I'm not really sure. I can think of one notable case like this with VMware being sued by a Linux kernel dev for code that is suspiciously similar. I don't know if they have resolved that yet though.

https://sfconservancy.org/copyleft-compliance/vmware-lawsuit-faq.html

>>61047823
>32TB is likely not even a day or two of builds. Sorry to burst your bubbles kids, there's nothing special about these builds. They're all public releases! I just looked over them and they're an archive of the Redstone and Threshold builds for Insiders. Literally nothing special to see here. https://www.betaarchive.com/forum/viewtopic.php?f=2&t=6083&sid=00a32396bc394ba55703990b704c254a&start=450 The builds from [rs|th]*_[pre]release are insider builds.
>After reading the engineering blogs for long enough, they have a build infrastructure that churns out something on the order of a few thousand builds a day all with different version numbers (rs3_prerelease and feature2, two public branches for the desktop and mobile builds, respectively) get builds for Mobile, Server, Desktop, IoT in many cases, Embedded, etc. for x86, x86_64, ARM, ARM64, probably some other stuff in there too.

>>61047823
Someone can find the botnet now

File: 1475919320190.jpg (54KB, 480x451px) Image search: [Google]

54KB, 480x451px

>>61049909
>google image search result

>>61047868
>>61048172
>peak at parts of the source code where your api is weak/missing
>don't mention that you peaked at it
Ez

>>61047868
I know that.
But, is there any workaround it can be used?

>>61050154
only the files werre removed as soon as they were found. the NSA and Microsoft are arresting people in the UK right now.

They cant keep getting away with this

>>61049722
When Microsoft sues you in a civil case for using their source code, you have to prove you didn't. If you didn't actually reverse engineer anything then you'll have no legal legs to stand on.

>>61051566
>guilty until proven innocent

>>61051574
When you're an adult you'll learn the difference between criminal court and civil court.

>>61050136
>I went through everything this morning. Unfortunately, the leaks appear to be nothing substantial.
The memes strike back

>>61050186
Having one person look at the code and describe what it does to another person who doesn't look at the code maybe

>>61049612
Maybe you could stop calling people retards and provide an actual argument.

How's it look? I bet it's pajeet-tier spaghetti code with tons of lewd comments.

>>61047823
IT IS OVER
MICROSOFT B T F O
HOW WILL THEY EVER RECOVER
GNU/LINUX HAS WON

>>61047823
good, now we just need to debotnet it

>>61049183
no hardware is illegal

>>61047823

fuck yeah i cant wait for assange or snowden or even linus infront of the source code on big monitor and pointing at it with there barehands "see here normies see this line of code ? this is nsa botnet right here - this line of code is where the government spies on you"

wait why cant reactos people look at the source code? cant we just fork it?

File: that_smile.jpg (23KB, 484x349px) Image search: [Google]

23KB, 484x349px

>>61048972
>>61047868
>>61050186
>>61049780
This is Reddit-tier naivety. Holy shit, you guys are stupid as fuck.

You're like the people who were asking if replacing their game discs mean they have to redo their backups.

>>61048709
>it would take me 5.3 years (64 months) because of data caps
great!

>>61050179
Most developers in the reactos project use windows and microsoft cares about what they are doing so they are pretty much heavily monitored.

If they peak at it expect them to get fined to oblivion

>>61050179

I think the problem comes down to how vague this shit can get, to the point where it doesn't even need to copy anything to trigger copyright infringement.

Look at the lawsuit of Bethesda v Facebook over VR technology.

Bethesda won that lawsuit despite the Oculus containing literally NOTHING taken from Bethesda, they won on the claim that John Carmack had learned some stuff about VR at Bethesda and after coming to Facebook he may have used what he learned to possibly have ideas about how to handle VR for the Oculus Rift.

They basically won on the idea of "VR was researched when you worked here, now you can never, ever do anything VR related again in your life because it can use concepts you passively learned while here".

The very idea that if while at Bethesda someone said "The camera in game should tilt when your head does" to him (an obvious thing that everyone would know intrinsically when it comes to VR design) now he can literally never apply that obvious concept to anything ever again or Bethesda sues.

I doubt having a third party convey ideas from their code isn't going to be exactly as above. It's still some sort of nebulous "mind share" of concepts from one company to another that is apparently illegal.

>>61048533
you can toats generating working source from pdbs

Protip: They leaked this to intentionally get the legal framework to sue reactOS

>>61053980
Imagine being this paranoid.

ReactOS is not a threat to Microsoft. OEMs are never going to switch to it because Microsoft charges them almost nothing for Windows licenses now that they make most of their money selling your data. Gamers are never going to switch to it because it's not compatible with Windows 10 or even 7/8.

>>61047823
link or this is viral marketing/some sort of false flag shit by M$

>>61054035
soon?

>>61054104
http://www.theregister.co.uk/2017/06/23/windows_10_leak/

>>61053980
How is a leak ReactOS devs won't touch going to make MS more likely to win a lawsuit against them?

>>61054286
Because law isn't fair, that's why. Lawyers can now scrutinise parts of ReactOS code looking for relative matches with parts of the leaked win10 code, and through the power of money force a court decision to shut reactOS down.

>>61054307
If that's the game MS wanted to play they'd have compared the Win2k leak to it or leaked XP and gone after them.

>>61047823
actually, leaking old code is a good way to setup a potential law suit 10 years down the line.

>>61049769
>micro$oft is big enough to survive an expensive lawsuit even if they lose

at that point, the government should be stepping in and breaking up microsoft into smaller companies, like teddy roosevelt used to do

that motherfucker was a great president

>>61054285
link to the leak dumb nigger

>>61054286
because now microsoft can bring a case where immediately the assumption is that they DID peek at the code, and ReactOS would have to prove otherwise.

>>61054383
But why would they leak Windows 10 source code when ReactOS devs are targeting XP? Again, they'd have leaked XP if that was their intention.

>>61054285
Link to the files

win 10 featherweight tinfoil edition when

I really want that Shared Source Kit

>>61054035
>Gamers are never going to
>it's not
Pick one tense and only one, friendo.

>>61051771
This is the only acceptable method for reverse engineering in the U.S.

>>61047823
So where can I download it? Piratesbay?

>>61057289
It's pointless to download this shit....

>>61047823
>ReactOS getting a bump in 3...2...1...
Lawsuit.

The devs are retarded for even making ReactOS in the first place, but they're still not stupid enough to use actual Windows source code.

>>61057370
Didn't they get accused of stealing code before, the project got halted and they had to do a full audit?

>>61047823
you DO realise that everytime this happens React OS development stalls because they are forced to audit under threat of litigation?

Microshit knows this and pulled this stunt ON PURPOSE

>>61050179
peek