Windows XP leak confirmed after user compiles the leaked code into a working OS

Re:Windows XP leak confirmed after user compiles the leaked ... by phoe-krk on Wednesday September 30, 2020 @01:50PM (#24641470)

Same as Wine: none, since they are required to be 100% black-box reimplementations. No one who contributes to Wine is allowed to even look at the original Microsoft source code.

[ Parent | on HN ]

Re:Windows XP leak confirmed after user compiles the leaked ... by aloknnikhil on Wednesday September 30, 2020 @02:03PM (#24641629)

Curious, how do they enforce this? Or is it just assumed in good faith?

[ Parent | on HN ]

Re:Windows XP leak confirmed after user compiles the leaked ... by Bancakes on Wednesday September 30, 2020 @02:06PM (#24641670)

While I haven't seen such a case, I can imagine a mailing list 'leaking' with posts like "like the trick Windows did for fast_malloc()" and such, then being summoned.

[ Parent | on HN ]

Re:Windows XP leak confirmed after user compiles the leaked ... by pmarin on Wednesday September 30, 2020 @02:06PM (#24641672)

https://en.m.wikipedia.org/wiki/ReactOS#Internal_audit

[ Parent | on HN ]

Re:Windows XP leak confirmed after user compiles the leaked ... by Sohcahtoa82 on Wednesday September 30, 2020 @02:20PM (#24641835)

Don't you mean black-box reimplementations? White box would mean they have access to and use the source code. Black box means they don't.

[ Parent | on HN ]

Re:Windows XP leak confirmed after user compiles the leaked ... by phoe-krk on Wednesday September 30, 2020 @02:24PM (#24641887)

Thanks; fixed the original post.

[ Parent | on HN ]