Re:32TB of Windows 10 internal builds, core source code leak...
by wfunction on Friday June 23, 2017 @10:03PM
(#14624027)
> 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...
by pmontra on Saturday June 24, 2017 @01:32AM
(#14624492)
This is what they did https://www.reactos.org/wiki/Audit
Re:32TB of Windows 10 internal builds, core source code leak...
by wfunction on Saturday June 24, 2017 @01:38AM
(#14624510)
That's pretty cool, thanks!
Re:32TB of Windows 10 internal builds, core source code leak...
by ClassyJacket on Friday June 23, 2017 @11:27PM
(#14624238)
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).
Re:32TB of Windows 10 internal builds, core source code leak...
by krylon on Saturday June 24, 2017 @05:00AM
(#14624947)
IANAL, but as far as I understand the situation it is not. See https://en.wikipedia.org/wiki/Chinese_wall#Reverse_engineeri...
But IIUC, clean room reverse engineering requires substantial effort to prove you did not take any shortcuts.
If anything, this could make their legal situation more sticky.