SMSS & LSASS: Service Status

[Rick Langschultz]

Hey all,

I am thinking about starting, or helping write the SMSS and/or LSASS  
implementation on ReactOS. I was wondering what I can help with, or  
help someone to do the work...

Rick Langschultz
[e-mail] (Home)
[e-mail] (Work)
[e-mail] (School)

[Andrew Murphy]

Excuse my ignorance, what do these do?

On 03/09/05, Rick Langschultz [e-mail] wrote:
> Hey all,
>
> I am thinking about starting, or helping write the SMSS and/or LSASS
> implementation on ReactOS. I was wondering what I can help with, or
> help someone to do the work...
>
> Rick Langschultz
> [e-mail] (Home)
> [e-mail] (Work)
> [e-mail] (School)
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Oliver Schneider]

> Excuse my ignorance, what do these do?

LSASS = Local Security Authority Sub-System
SMSS = Session Manager Sub-System
-- 
---------------------------------------------------
May the source be with you, stranger ;)

ICQ: #281645
URL: http://assarbad.net

[Emanuele Aliberti]

Rick Langschultz wrote:
> Hey all,
>
> I am thinking about starting, or helping write the SMSS and/or LSASS  
> implementation on ReactOS. I was wondering what I can help with, or  
> help someone to do the work...

For what I am aware of, the SM needs:

1) implementing delayed move file: the only file involved should be 
trunk\reactos\subsys\smss\initmv.c (Recently Steven Edwards implemented 
the delayed move file in the Win32 client library, porting some WinE 
code; if the SM performs the actual move during the bootstrap, we will 
be able to release service packs for ReactOS);

2) peer revieweing the client management code and the SM API in general 
(Suggestions, hints, proposals, questions, code welcome! This is a 
really broad subject, because of the key rôle the SM has in managing 
multiple personalities; the SM interacts with NTOSKRNL, the user mode 
loader in NTDLL, per personality debuggers; per personality subsystem 
servers).
-- 
:Emanuele Aliberti

[Casper Hornstrup]

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Emanuele
> Aliberti
> Sent: 3. september 2005 17:46
> To: ReactOS Development List
> Subject: Re: [ros-dev] SMSS & LSASS: Service Status
> peer revieweing the client management code and the SM API in general
>
> (Suggestions, hints, proposals, questions, code welcome! This is a
> really broad subject, because of the key rôle the SM has in managing
> multiple personalities; the SM interacts with NTOSKRNL, the user mode
> loader in NTDLL, per personality debuggers; per personality subsystem
> servers).

Speaking of debuggers, I would welcome an implementation of some debugger
APIs. I really have no idea of which APIs or how to use them. All I know
is that I need to be able to have reporterror.exe run and attach itself
to a process when the process experience an unhandled exception.
Reporterror.exe can then grab the register information and resolve the
stack trace using rsym symbol information and publish it to the ros-errors
mailing list.

Casper

[Saveliy Tretiakov]

Support for usermode debugger would be great! It will be very useful thing.

Casper Hornstrup wrote:
> > -----Original Message-----
> > From: [e-mail] [mailto:[e-mail]] On Behalf Of Emanuele
> > Aliberti
> > Sent: 3. september 2005 17:46
> > To: ReactOS Development List
> > Subject: Re: [ros-dev] SMSS & LSASS: Service Status
> > peer revieweing the client management code and the SM API in general
> >
> > (Suggestions, hints, proposals, questions, code welcome! This is a
> > really broad subject, because of the key rôle the SM has in managing
> > multiple personalities; the SM interacts with NTOSKRNL, the user mode
> > loader in NTDLL, per personality debuggers; per personality subsystem
> > servers).
>
> Speaking of debuggers, I would welcome an implementation of some debugger
> APIs. I really have no idea of which APIs or how to use them. All I know
> is that I need to be able to have reporterror.exe run and attach itself
> to a process when the process experience an unhandled exception.
> Reporterror.exe can then grab the register information and resolve the
> stack trace using rsym symbol information and publish it to the ros-errors
> mailing list.
>
> Casper
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev