Ros-dev

ros-dev@reactos.org

2 participants
5791 discussions

LSASS and MSV1_0.DLL - more research
by Luke Kenneth Casson Leighton 10 Sep '05

10 Sep '05

lots of people appear to have done quite thorough amounts of digging into MSV1_0.DLL due to it being the key to security attacks and stuff e.g. http://www.security-protocols.com/whitepapers/NT/NTcred.txt the two that i have read so far describe how WINLOGON.EXE is a "user" of the LSASS system by doing a LsaLookupAuthenticationPackage call, in order to obtain, presumably, the vector-table which MSV1_0.DLL registers with the LSASS, and then once that vector-table is obtained, they then go on to describe how MSV1_0.DLL may be attacked, by describing in detail the data structures in it. how very convenient for actually implementing one :) l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

samba tng program compile status
by Luke Kenneth Casson Leighton 10 Sep '05

10 Sep '05

hi, thought people might want to know: rpcclient.exe already was confirmed as working (by elrond) i just successfully compiled and tested smbclient, that works too. rpcclient.exe produces a _beautiful_ blue screen, i fell about when i saw this. elrond has a patch for smbd which removes fork() and i want to try this out and also make the msrpc services do the same thing, that will be fuuun. the sooner someone gets freedce to compile on mingw32 the damn better is all i can say there. i found some example code that uses NamedPipes i intend to add that in at both the client side and the server side and see what breaks, oo that will be fun i've never done nt named pipes programming before. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

Re: SMSS & LSASS: Service Status
by Luke Kenneth Casson Leighton 10 Sep '05

10 Sep '05

regarding your offer to help with LSASS.... GREAT! because, coincidentally, this is exactly one of the areas required to tie in MSV1_0.DLL which will be a registererer with the LSASS, and MSV1_0.DLL is where all the nt authentication stuff happens. great, great. okay, here's something i found which describes the process, it looks pretty damn good: http://www.coresecurity.com/common/showdoc.php?idx=87&idxseccion=11 now, here's the bit that you _don't_ have to do: you do NOT have to do _any_ of the bits _behind_ "access the sam database". all of that is already written for you - in samba tng. i've had a _brief_ look at the implementation of lsass in reactos, and i believe it to be pretty good. it's just that there are no "registerers" e.g. there is no implementation of MSV1_0.DLL. l. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

1 0

Can someone send me the MS sound blaster driver example code?
by Andrew "Silver Blade" Greenwood 09 Sep '05

09 Sep '05

Someone sent me this a while back, but I lost it. Basically I believe it was from a MS DDK, and it contained code for MMDRV.DLL and SNDBLST.SYS. At the time I was feeling lazy and just clumsily hacked in whatever I felt like, without any order to what I was doing. I want to have another stab at it, by reviewing the existing code, documenting it for my own understanding, and then writing my own solution. So if someone could send me those files, I'd appreciate it! -Andrew PS: The files in question were NOT obtained from the leaked Windows source code.

1 0

Frequent commits?
by Reuben Perelman 09 Sep '05

09 Sep '05

Lately I've seen a lot of updates to svn. Is it just a lot of work being done, or is there some type of revert war?

3 3

Re: [ros-svn] [hpoussin] 17751: Fix build, by correcting include paths and updating xml files of USB components
by TwoTailedFox 08 Sep '05

08 Sep '05

Corrected, just as I was trying to work out while it wasn't compiling with Mingw ;) On 9/8/05, hpoussin(a)svn.reactos.com <hpoussin(a)svn.reactos.com> wrote: > Fix build, by correcting include paths and updating xml files of USB components > > > Added files: > trunk/reactos/drivers/usb/usbport/usbport.def > > Updated files: > trunk/reactos/drivers/usb/miniport/linux/pci_hal.c > trunk/reactos/drivers/usb/miniport/usbohci/ohci-hcd.c > trunk/reactos/drivers/usb/miniport/usbohci/ohci_main.c > trunk/reactos/drivers/usb/miniport/usbohci/usbohci.xml > trunk/reactos/drivers/usb/miniport/usbuhci/uhci-hcd.c > trunk/reactos/drivers/usb/miniport/usbuhci/uhci.h > trunk/reactos/drivers/usb/miniport/usbuhci/usbuhci.xml > trunk/reactos/drivers/usb/usbhub/usbhub.h > trunk/reactos/drivers/usb/usbhub/usbhub.xml > trunk/reactos/drivers/usb/usbport/buffer_simple.c > trunk/reactos/drivers/usb/usbport/config.c > trunk/reactos/drivers/usb/usbport/core_drivers/usbkey.c > trunk/reactos/drivers/usb/usbport/core_drivers/usbmouse.c > trunk/reactos/drivers/usb/usbport/hcd-pci.c > trunk/reactos/drivers/usb/usbport/hcd.c > trunk/reactos/drivers/usb/usbport/hub.c > trunk/reactos/drivers/usb/usbport/message.c > trunk/reactos/drivers/usb/usbport/urb.c > trunk/reactos/drivers/usb/usbport/usb-debug.c > trunk/reactos/drivers/usb/usbport/usb.c > trunk/reactos/drivers/usb/usbport/usbcore.c > trunk/reactos/drivers/usb/usbport/usbport.xml > > Deleted files: > trunk/reactos/drivers/usb/usbport/usbcore.def > > _______________________________________________ > Ros-svn mailing list > Ros-svn(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-svn > -- "I had a handle on life, but then it broke"

1 0

Re: [ros-svn] [ion] 17727: Implement NTDLL's CSR routines in a compatible way. Fix prototypes, argument count, deprecated functions and new functions. Some functions will not work (or are designed not to work) fully until the new CSR is committed, but they keep the same functionality as the previous versions (no regressions found; tested with cmd, cmt, putty, telnet, ps). Also added NtSecureConnectPort.
by Hartmut Birr 08 Sep '05

08 Sep '05

Hi, this changes does break booting for me. I get an error message: (subsys\csrss\api\wapi.c:198) CSR: NtListenPort() failed, status=c0000005 - Hartmut

3 3

Replacement for Bitstream fonts
by Mikhail Y. Zvyozdochkin 08 Sep '05

08 Sep '05

Hi All. I think it's a good idea to use Dejavu fonts http://dejavu.sourceforge.net/ instead Bitstream Vera. Reasons are: - it based on Bitstream fonts (1.10); - it's distributing under SAME license; BUT - it supported MUCH more unicode pages than original Bitstream fonts; it was main goal of Dejavu Projects "to provide a wider range of characters", to support various languages and codepages. In particular, I tried to activate Russian language in ReactOS 0.2.7-REL with Dejavu fonts. It working correctly without any proprietary fonts :). Unicode coverage table: http://cvs.sourceforge.net/viewcvs.py/*checkout*/dejavu/dejavu-fonts/unicov… At this September they want make new release, 1.14. I think, it new version may be integrated with ReactOS 0.3 :) WBR, DarkHobbit

1 0

problem with current svn
by Hartmut Birr 08 Sep '05

08 Sep '05

Hi, I'm trying to compile ros on ros with the current svn tree. It isn't possible. After some time, it fails with a message cannot execute 'bla bla'. The build does corrupt the file system. If I run chkdsk from w2k I get many messages about multiple files like 'wrc.ex'. It seems that something is wrong with the string functions. - Hartmut

3 5

RE: Ros-dev Digest, Vol 13, Issue 14
by Lucio Diaz 08 Sep '05

08 Sep '05

Sorry, but i still cant see the point. 0.2.7 is a release, and thus is oriented to the user (maybe power user or fan at this moment), to test and play around. Users, like me, dont go to bugzilla cause most of us can not make sense of all that techicall information. I knew there was a problem, a blocking problem for anyone trying to install the OS in real hardware and i wrote about it where a user (like me) may find out, in the wiki. I can not understand why you become angry. I am just filling some documentation for the user, and that is the only whay i can colaborate ( i doubt you would apretiate my little pascal and delphy coding skill). Known problems is for that... enumerating the known problems of a determinated version, while 0.2.7 is the last version i consider relevant the fact that it can not be installed in Real Hardware. I wish i could debug and find the problem, but i dont have the experience or the tools to do so. with my best wishes to the team, Lucio Diaz. WaxDragon wrote--> Message: 5 Date: Wed, 7 Sep 2005 13:15:19 -0400 From: WaxDragon <waxdragon(a)gmail.com> Subject: Re: [ros-dev] RE: Ros-dev Digest, Vol 13, Issue 13 To: ReactOS Development List <ros-dev(a)reactos.com> Message-ID: <9b0d5f3205090710157abc163f(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 I think you missed the point. I'm talking about http://www.reactos.com/wiki/index.php/Known_Problems When calling things "known problems" I want bugs for them. I'm going to assume you are talking about this known problem: http://www.reactos.com/bugzilla/show_bug.cgi?id=688 Which was even noted on the 0.2.7 changelog page: http://www.reactos.com/wiki/index.php/ChangeLog-0.2.7#Known_Bugs PLEASE, if you write ANYWHERE that ReactOS has a "known bug" please provide a link to the bug in bugzilla. If there is no bug in BugZilla, then there is a great possibility the Testing team doesn't know about it. By filing bugs, we can reduce the amount of duplicate effort required to fix said bug. When filing bugs, please review http://www.reactos.com/wiki/index.php/File_Bugs first. With that out of the way, I know that noone has looked at that bug since 0.2.7 was released. If you can gather any useful info about the hardware (the i8042 controller specifically) that you are experienceing the problem with, update the bug, this may help with getting it resolved. WD PS. I'm very tempted to make the "Know Problems" page go away, or heavily modify it. ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Ros-dev