![]() “The talk presents the goals of the project, the current status and the challenges related to reverse-engineering the badly documented Windows API.”Īnd all the above posts talk about dirty reverse engineering of the actual windows files, not about reverse engineering 3rd party applications and drivers, as ReactOS development team does to ensure compatibility! The last for now topic stating Wine is a reverse-engineering effort: ![]() Here Schachar Shemesh makes statement that it is impossible to develop Wine withour reverse engineering, and if Wine’s code is cleaned from reverse engineered code, then no code will left at all.Īnd this person’s patches are in official Wine repository! (It’s no doubt he is a reverser). And it shows a clear proof that dirty reverse engineered code made it into Wine without any problems. This one really shows how Steven Edwards (our project coordinator) cared about legality of source code. “And without reverse engineering, you wouldn’t have the beautiful thing known as WINE here before you” It is obvious that I won’t allow dirty reverse-engineered code enter in ReactOS repository, it’s as clear as a pure water.įinally, about reverse engineering and mailing list posts, let us look into Wine’s mailing list archive: kdcom.sys by Alex from Windows 2003SP1 can make it’s use in ReactOS, and make it tainted. Also, we work a lot with Wine’s regression tests to fix modules of the system we naturally can’t share with Wine and have to implement in Windows-specific way.Īs for TinyKRNL: I don’t understand the concern about it, because it doesn’t contain ANY reverse-engineering of a kernel (which is the only part Alex Ionescu develops now in ReactOs), and secondly, if I do my personal education project on creating a fully compatible with Windows2003 HAL implementation, I certainly understand that I will never have the right to develop ReactOS’s HAL. ![]() Not only it provides us a legal-ground, but it sets development to a new position, when no regress happens. Wine does now, and I’m gathering now various test applications our developers use, reformat them to match the kernel-mode regression framework and commit to the repository. The main strategy is to use regression-tests as We are in the process, but so far everything looks rather good, and if we find any suspicious code, we will ask a 3rd-party developer to rewrite it. However, by that time we already have a few millions line of code codebase in the repository, so we decided to perform an auditing process, to see parts of the code which might have unclean origin. By the time I came into a project coordinator’s position, commiting directly reverse engineering code is forbidden in ReactOS. That’s as simple to verify as Julliard told in his interview: ask a few questions, and you see if the guy really developed the code, or he copy-pasted from leaked source code.Īs for reverse-engineering: This is a very interesting topic. And people who I don’t trust will never get commit-access or their patches commited. ![]() And every developer in my team clearly udnerstands, that if he starts using leaked source code even for studying, that will eventually ruin the project. Not because it’s greatly confusing, but because you dare to provide links and quotes from that provocation we had in January.Īs a project leader, I officialy state, and will state again and again when it’s needed and in question: ReactOS NEVER UTILISED ILLEGALY OBTAINED source code (like Windows NT 4 or 2000 “leaked” source code). I’m really sorry I was pointed out to your post by our developers. Let’s wait and see if the following like ever gets updated: So back to our story, I thought, why worry about my reverse engineering? Some of us have done much worse.” As for XXXXX, last I know he attempted to get the NT4 source compiling, a feat which I had tried as well. I do not think that nor XXXXX nor I did anything wrong: he only gleaned through some files and quite probably did not learn anything useful, and the only code I looked at were some libraries which I do not touch: In the end, he realized that doing this was wrong, and he deleted his copy. XXXXX then told me he was interested about looking at the DCOM source code, document it, and then help WINE out with it, all while taking a 6 month leave to do so. “Likewise, I joked with XXXXX about funny comments in some win32 DLL source code which I knew I would never implement. “I post here a mail which Alex has sent to the ‘inner circle’ of ReactOS.” I refer you to the deleted message, which I have the contents of:
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |