That list isn't "mine", it's a collection of proposals from several people. The only two entries that I can claim any familiarity with are the performance data registry and UEFI booting.
On Tue, Mar 5, 2013 at 12:22 AM, J. C. Jones <[email protected]> wrote: > Hi Zachary, > > > > I noticed one item on your list that might be relevant to a problem that I > am having with setting up remote-debugging between a host machine running > Windows 7 and a guest machine running ReactOS: > > > > Security Controls > > Implement support for user permissions based on Access Control Lists. > > Benefits > > This will allow separation of users into groups and better control over user > privileges in ReactOS. Security controls will then allow supporting multiple > users on the same system. > > Skills Needed > > Familiarity with Windows security and permissions models > > > > See my post: > > > > http://www.reactos.org/forum/viewtopic.php?p=99347#p99347 > > > > While trying to induce Visual Studio, running on a Windows 7 host, to show a > list of all running processes on a ReactOS VM, Visual Studio, is indeed, > communicating with MSVSMON.EXE, the server process on the ReactOS VM, and > even connecting to it. Then, suddenly, Visual Studio puts up a dialog box > that says that the IP address of the ReactOS VM is invalid, which is > obviously not true, because, concurrent with this error message, MSVSMON.EXE > shows in its log window that it just connected to the Visual Studio running > on the host. > > > > I suspect that MSVSMON.EXE is trying to gain SeDebugPrivilege to one or more > processes running in ReactOS to which it is not entitled. When MSVSMON.EXE > receives an error code from one of the access control functions, it sends > error message back to Visual Studio. Visual Studio is caught off-guard by > this error message and gives a bogus explanation for failure. > > > > Does ReactOS support the Authorization Functions, and AdjustTokenPrivileges > in particular? Does this explanation for the failure make sense? > > > > Cheers, > > > > -John (A.K.A. BlackRabbit) > > > > From: [email protected] [mailto:[email protected]] On > Behalf Of Zachary Gorden > Sent: Saturday, March 02, 2013 4:01 PM > To: ReactOS Development List > Subject: Re: [ros-dev] Google Summer of Code 2013 > > > > Note that I've already created an ideas page for 2013 here: > http://reactos.org/wiki/Google_Summer_of_Code_2013_Ideas > > On Sat, Mar 2, 2013 at 3:54 PM, Colin Finck <[email protected]> wrote: > > Hi all, > > Google will host its Summer of Code again this year. Let's try to get in > again after our successful participation in 2011! > > Who's available to write up a new idea page along with the student guide? > Let's draft it in a Google doc again. > I believe that some more ideas can be added, i.e. tasks on Explorer-New now > that work has progressed on it. Others need to be removed, such as the > finished AHCI support for UniATA or my KD USB-to-Serial driver, which nobody > really understood ;) > > Deadline is 18th March, so about 2 weeks to go. > > References: > * http://reactos.org/wiki/Google_Summer_of_Code_2012 > * http://reactos.org/wiki/Google_Summer_of_Code_2012_Ideas > > > - Colin > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://www.reactos.org/mailman/listinfo/ros-dev > > > > ________________________________ > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2013.0.2899 / Virus Database: 2641/6147 - Release Date: 03/04/13 > > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://www.reactos.org/mailman/listinfo/ros-dev _______________________________________________ Ros-dev mailing list [email protected] http://www.reactos.org/mailman/listinfo/ros-dev
