Re: [ossig] Secret Windows Code Leaked On Internet

[Uwe Dippel <udippel@xxxxxxxxxxxxx>]

Dinesh Nair wrote:

> i believe imran was referring to taking portions of the leaked source and
> using it in an open source project, not necessarily using it on the
> windows platform per se.

Which so ever ...

  in the latter scenario, microsoft may hit you
> with their anti-reverse engineering provisions part of the EULA.

Dinesh, I was under the impression we had it on 'hiring'. At least, my 
argumentation was about that.
With the best of intention, once you know a solution to a given problem 
it is very hard to 'forget' that solution on purpose, in order to write 
one that is not derived from the first one.

> proof has to be rock solid for this, and with the exception of the
> programmer making the silly mistake of cut-n-paste, there is no violation.

The programmer hired by me and knowing about 'that secret sys_call' will 
be less productive than the one untouched; because the latter doesn't 
need time to forget and won't while time away thinking: 'what a bunch of 
buggers not to permit me to use this.'
The latter will simply sit with the problem and - more importantly even 
than productivity - I can be sure that no infringement happens.

> obviously, to be _absolutely_ sure, you'd need to clean room any
> implementation, but in reality this is harder done than said.

The more the programmer is a 'virgin' on Windows code, the cleaner the room.

Uwe,

who's still waiting for the first reports of code quality. Would be fun 
to know that they have trunks of dead code lying around for the simple 
purpose that the compilation dies once it is removed !


---------------------------------------------------------
To unsubscribe: send mail to ossig-request@mncc.com.my
with "unsubscribe ossig" in the body of the message