Salutations from the ReactOS project team! In previous posts, we talked about the ReactOS releasing process and the development status of the project, as well as the hiring of our long-term developer Hermès Bélusca-Maïto (HBelusca). We are making an effort to publish at least 3 newsletters per year, depending on how the development workflow goes. In this newsletter we will highlight some of the contributions made by project developers and contributors, as well as future plans and headlines.
Hello ReactOS followers and enthusiasts! It has been quite a long time since we published the 101th newsletter and so far no further updates have been posted since then. While the ReactOS Twitter account does provide announcements, posts about working applications and such from time to time, much of what is happening with the project as a whole isn’t mentioned. Most of what we are going to talk about is the current situation with releases and overall ReactOS development.
Hello ReactOS followers! This report covers changes in the project during February-July 2021. And we definitely have some things to highlight! amd64 build is getting more stable Timo Kreuzer (tkreuzer) worked hard on various parts of the kernel and HAL, fixing issues here and there. Structured Exception Handling (SEH) support for the amd64 architecture was finished, various bugs around the kernel are fixed. A major issue with interrupt handling in HAL was also fixed in May, which finally allowed a semi-stable boot in a virtual environment.
Hello ReactOS followers! This is an attempt to re-instate the Newsletter, which informed you about recent developments. The previous Newsletter 99 was in 2013! This month we were mostly focused on the kernel work, merging pull requests and fixing regressions. Memory manager and Common cache work Being in development for almost six month, this work by Jérôme Gardou finally landed in the master branch. This change refactors many aspects of the Section Objects feature in NT-compatible kernel, making it more compatible with Windows.
Hello everyone, I am Suraj K Suresh, the one working on the GSoC project of “Porting Syzkaller to ReactOS”. It’s been 3 whole months since GSoC has begun and this is the last evaluation period. During the last 3 months, I worked on various parts of Syzkaller and getting them up and running on ReactOS and Windows with the help of my Mentors. This blog post will be a wrap-up post of the GSoC project.
After 3 months since the last blog, I found and pull the patches of 12 memory disclosure bugs: [NTOS:PS] Fix stack memory disclosure in PsGetContextThread: merged [Win32SS][USER] Fix stack memory disclosure in NtUserBuildPropList: merged [MOUNTMGR] Fix pool memory disclosure in QueryPointsFromMemory: merged [Win32SS][GDI] Fix pool memory disclosure in NtGdiGetGlyphOutline: merged [DRIVERS] Fix pool memory disclsoure in CreateDiskDeviceObject of disk driver: closed [NTGDI] Fix stack memory disclosure in NtGdiGetTextMetricsW: merged [NTOS:KE] Fix stack memory disclosure in KiInitializeUserApc: merged [NTOS:IO] Fix pool memory disclosure in IopQueueTargetDeviceEvent: merged [Win32SS][GDI] Fix pool memory disclosure in NtGdiGetOutlineTextMetricsInternalW: merged [WIN32SS][NTUSER] Fix uninitialized memory cause memory disclosure used for KeUserModeCallback: merged [FILESYSTEMS] Fix pool memory disclosure in filesystem drivers supporting FS_INFORMATION_CLASS.
Hi, I’m He Yang (@kernel.bin), one of the GSoC-2020 students of ReactOS. How time flies, three months have passed and now GSoC is coming to an end. During the last three months, I’ve been working on rapps, and I’ve made some small progress on it: improving rapps by increasing it’s functionality, stability, and make the code more well-organized. During GSoC, I’ve acquired a lot of coding skills and knowledge about Win32.
Hello everyone. In this blog post, I will be talking about the steps to set up Syzkaller for ReactOS locally and start fuzzing. If you have been following the blog posts on the ReactOS website then you would have noticed that this is my Google Summer of Code 2020 Project. Now that Coding period 2 has officially come to an end and the work is nearing completion, this post will help others in setting up the fuzzer get started with fuzzing.
Hi, I’m He Yang (@kernel.bin), one of the GSoC-2020 students of ReactOS. Two months have passed since GSoC started, and during these two months, I’ve made some progress on ReactOS Application Manager (RAPPS), the project I’m working on. In this blog, I will list out what I’ve accomplished in these two months, and what I’m planning to do in the next month. The work I’ve done in Stage 1&2 Stage 1 During stage 1, I mainly focused on screenshot and icon support and various small improvements.
Hey, I am Suraj K Suresh (@Freakston), In this post I’m going to be listing out what I’ve completed in Coding period-1 of GSoC. Status The initial part of setting up Syzkaller and being able to fuzz ReactOS is done. The link to grab ReactOS compatible syzkaller is as follows: Github. The detailed instruction on setting it up can be found here. Work-done Boot ReactOS with UBSan enabled. The branch which has UBSan enabled can be found in extravert34’s fork of ReactOS.