Hi,
if I compile MC (midnight commander ) with the option
'-mpreferred-stack-boundary=2', the build-in editor doesn't work. MC
hangs after pressing F4. This occurs on winXP and ROS. I've no problem
without this option.
- Hartmut
New ReactOS Homepage - Status
Mail-Content:
* Status
* Questions
Homepage status:
The homepage beta test started last week. Join #reactos-hp for more
information. We will start reviewing and translating the content in a few
days.
Content List: http://www.reactos.com/wiki/index.php/New_Homepage_Content
When this is done (approximatly one week) we will be able to relaunch the
homepage!
Homepage release date: "When it's done!" ;)
Questions:
1) Should the homepage section be called ... ?
a: developer
b: development
c: developing
2) Should the static homepage pages be ... ?
a: valid HTML 4.01
b: valid XHTML 1.0
c: both variants (two versions)
d: something else (e.g. xhtml 1.1)
3) What's your opinion about the following homepage content structure ... ?
* Home
* Community
* Support
* Developer / Developing / Development
* myReactOS
(more details: http://www.reactos.com/wiki/index.php/New_Homepage_Content )
a: okay, good structure
b: ... -> then edit/add comments to the wiki page see link above !!!
Klemens Friedl
--
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse f�r Mail, Message, More +++
This is the most ugliest beast I've come across.
Trying to implement parts of the Kernel Streaming (ks) stuff. I decided
to start with portcls.sys.
So far, it appears ks.h (the Kernel Streaming main header) isn't present
in our include files (or w32api) and the official MS DDK version is
100KB + so that's a bit of a knock-out already.
Anyway I had a poke around and stubbed a lot of the main portcls.sys
functions. But I have no idea what I'm doing right now so it's pointless
me trying.
It appears to be built on COM - the MSDN documents describe "Kernel-mode
COM" in the Audio and Video section.
Obviously the standard COM calls can't be used in kernel-mode. And I
found in kcom.h some declarations for functions such as KoCreateInstance
(kernel mode version of CoCreateInstance?) yet I cannot find any
references to it on Google.
The sample drivers are written in C++, and appear to rely on kcom.h's
C++ classes to get things done.
There's just not a lot I can do as the foundation isn't even there for
me to start implementing Kernel Streaming.
And I have *no* idea how to use COM. So far it looks really really ugly.
Can someone give me a hand?
-Andrew
royce(a)svn.reactos.com wrote:
>msvc6 compatibility and small performance improvement in filename completion
>
>Modified: trunk/reactos/subsys/system/cmd/internal.c
>
>
> *Modified: trunk/reactos/subsys/system/cmd/internal.c*
>
>--- trunk/reactos/subsys/system/cmd/internal.c 2005-09-12 14:55:55 UTC (rev 17818)
>+++ trunk/reactos/subsys/system/cmd/internal.c 2005-09-12 16:06:53 UTC (rev 17819)
>@@ -276,7 +276,7 @@
>
> TCHAR * tmpPath;
> TCHAR szCurrent[MAX_PATH];
> TCHAR szMsg[RC_STRING_MAX_SIZE];
>
>
>- INT i;
>
>
>+ UINT i;
>
>
>
>
> /* Filter out special cases first */
>
>
> ------------------------------------------------------------------------
If you change a variable from signed to unsigned, you have to check for
comparing with zero or negativ values like this:
/* Strip the paths back to the folder they are in */
for(i = (_tcslen(szFinalPath) - 1); i > -1; i--)
- Hartmut
Hey everyone,
I was just wondering how everyone got to reactos.com. I want to know
what Browser version people use and the operating system and/or the
operating system flavor you use. I know that many people are using
Linux, Windows, etc. But some browsers don't support some features
like some CSS tags and XMLHttprequest. But I was just wondering...
Maybe the web-development team could include in the future loggin
this and setting a cookie to not get 750 hits from the same computer
so the developers could develop software that would benefits most
users ie those that want to use firefox instead of IE and so on...
Rick Langschultz
rlangschultz(a)cox.net (Home)
rlangschultz(a)ellemaespa.com (Work)
rlangschultz(a)email.uophx.edu (School)
This time crash occured upon first movement of mouse during 2nd stage setup after "welcome" dialog had appeared ( hadn't touched mouse during bootup - if that makes a difference )
Looks like something related to the win32k refactoring maybe?
Assertion 'hdr->RefCount >= 1' failed at subsys\win32k\ntuser\object.c line 282
Entered debugger on embedded INT3 at 0x0008:0x800ab2b0.
kdb:> regs
CS:EIP 0x0008:0x800ab2b1
SS:ESP 0x45bc:0x800b4cdc
EAX 0x00000050 EBX 0x0000117d
ECX 0x00000000 EDX 0x000003f8
ESI 0x0064fc60 EDI 0x9e40bd74
EBP 0x9e40bbdc
EFLAGS 0x00000282 SF IF IOPL0
kdb:> bt
Eip:
<ntoskrnl.exe:ab2b1 ({standard input}:23 ())>
Frames:
<win32k.sys:abe21 (subsys/win32k/ntuser/object.c:282 (ObmDereferenceObject))>
<win32k.sys:8568f (subsys/win32k/ntuser/message.c:799 (co_IntPeekMessage))>
<win32k.sys:85c52 (subsys/win32k/ntuser/message.c:995 (NtUserGetMessage))>
<ntoskrnl.exe:93ec2 ({standard input}:177 (KiSystemService))>
<user32.dll:51a53 (lib/user32/windows/message.c:1166 (GetMessageW))>
<comctl32.dll:3d024 (lib/comctl32/propsheet.c:2770 (do_loop))>
<comctl32.dll:3d40d (lib/comctl32/propsheet.c:2897 (PropertySheetW))>
<syssetup.dll:4185 (lib/syssetup/wizard.c:1481 (InstallWizard))>
<syssetup.dll:1d39 (lib/syssetup/install.c:494 (InstallReactOS))>
<setup.exe:1355 (subsys/system/setup/setup.c:86 (RunNewSetup))>
<setup.exe:13c0 (subsys/system/setup/setup.c:122 (WinMain))>
<setup.exe:14eb (subsys/system/setup/setup.c:123 (WinMain))>
<setup.exe:120d>
<setup.exe:1258>
<KERNEL32.dll:307d5 (lib/kernel32/process/create.c:68 (BaseProcessStartup))>
<00000000>
kdb:>
Hey everyone,
I have a feature suggestion for version 1.0 or later... I think it
would be called the universal kernel. The kernel could be compiled
and made to run on various architectures: ia_32, ia_64, PPC, XBOX,
PPC64, etc. The computer would translate natively compiled files from
other systems into ia_32 or ia_64 code. I know that Windows XP (64
bit) uses WoW which allows 32 bit programs to access 64bit memory or
something like that. This way reactos could be installed on a variety
of systems with one installation disc instead of a flavor of that
disc. Just a suggestion for the future...
Rick Langschultz
rlangschultz(a)cox.net (Home)
rlangschultz(a)ellemaespa.com (Work)
rlangschultz(a)email.uophx.edu (School)
Rick Langschultz wrote:
> I was just wondering how everyone got to reactos.com. I want to know
> what Browser version people use and the operating system and/or the
> operating system flavor you use.
>
I'll play along :)
SuSE 9.3, Fedora Core 4 and Win XP ....
All running Firefox 1.0.6
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Hi,
calling RaiseException(EXCEPTION_ACCESS_VIOLATION,
EXCEPTION_NONCONTINUABLE, 0, NULL) from user mode does crash reactos.
- Hartmut
(lib\rtl\exception.c:29) RtlRaiseException(Status 0064fea8)
(lib\rtl\exception.c:36) ExceptionAddress 7c801fcc
(ntoskrnl\ke\exception.c:94) KiRaiseException
(ntoskrnl\ke\i386\exp.c:933) KiDispatchException() called
(lib\rtl\exception.c:75) RtlRaiseStatus(Status 0x80000002)
(lib\rtl\i386\exception.c:59) RtlDispatchException(): 87032998, 870326c8
(lib\rtl\i386\exception.c:64) RegistrationFrame is 0x87032D30
(lib\rtl\i386\exception.c:90) Invalid exception frame
(ntoskrnl\ke\exception.c:94) KiRaiseException
(ntoskrnl\ke\i386\exp.c:933) KiDispatchException() called
KeBugCheckWithTf at ntoskrnl\ke\i386\exp.c:993
A problem has been detected and ReactOS has been shut down to prevent
damage to your computer.
The problem seems to be caused by the following file: ntoskrnl.exe
Technical information:
*** STOP: 0x0000001E (0x80000002,0x80072fba,0x00000001,0x870329f0)
*** ntoskrnl.exe - Address 0x80072fba base at 0x80000000, DateStamp 0x0
Divide Error Exception: 0(0)
Processor: 0 CS:EIP 8:80072fba <ntoskrnl.exe:72fba
(ntoskrnl/mm/virtual.c:1002 (ProbeForRead))>
cr2 0 cr3 178f9000 Proc: 81ad12d0 Pid: 15c <t.EXE> Thrd: 81a691d8 Tid: 160
DS 10 ES 10 FS 30 GS 0
EAX: 870326c8 EBX: 81a691d8 ECX: 00000000
EDX: 000002f8 EBP: 81a691d8 ESI: 0064fbc4 ESP: 87032644
EDI: 87032d74 EFLAGS: 00000282 kESP 87032644 kernel stack base 87030000
Frames:
<0>
I rebuilt the bootcd, and installed on vmware - reformatted the hdd
during setup, and got this on first boot-up. I have the virtual machine
suspended if any other debug info is needed.
(ntoskrnl\ke\main.c:289)
---------------------------------------------------------------
(ntoskrnl\ke\main.c:290) ReactOS 0.3-SVN (Build 20050908-r17754)
Used memory 65536Kb
(ntoskrnl\mm\mminit.c:375) Kernel Stack Limits. InitTop = 0x8011c000,
Init = 0x80119000
(ntoskrnl\mm\mm.c:283) No current process
Entered debugger on embedded INT3 at 0x0008:0x800c6811.
kdb:> cont
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\pcnet.sys
(ntoskrnl\io\pnpmgr.c:1847) Initialization of service PCNet failed
(Status c0000001)
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\System32\DRIVERS\usbuhci.sys
(ntoskrnl\io\pnpmgr.c:1847) Initialization of service usbuhci failed
(Status c0000001)
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\pcnet.sys
(ntoskrnl\io\pnpmgr.c:1847) Initialization of service PCNet failed
(Status c0000001)
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\System32\DRIVERS\usbuhci.sys
(ntoskrnl\io\pnpmgr.c:1847) Initialization of service usbuhci failed
(Status c0000001)
(ntoskrnl\ldr\loader.c:252) Could not open module file:
\SystemRoot\system32\drivers\ne2000.sys
(ntoskrnl\io\pnpmgr.c:1847) Initialization of service Ne2000 failed
(Status c0000001)
(ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed
(Status c0000034)
(ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed
(Status c0000034)
(ntoskrnl\io\driver.c:1274) Driver 'buslogic.sys' load failed, status
(c0000001)
(ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed
(Status c0000034)
(ntoskrnl\io\pnpmgr.c:1847) Initialization of service serial failed
(Status c0000034)
(drivers\usb\usbport\usbcore.c:15) Miniport 0x80735BF0 registered
(drivers\usb\miniport\common\fdo.c:247) USBMP: unknown minor function 0x8
(drivers\usb\miniport\sys\linuxwrapper.c:479) IoGetDmaAdapter done
0x8074FC40, mapRegisterCount=2
(drivers\usb\miniport\usbuhci\uhci-hcd.c:2556) INF:
drivers\usb\miniport\usbuhci\uhci-hcd.c: USB Universal Host Controller
Interface driver v2.1
(drivers\usb\usbport\hcd-pci.c:74) usbcore: usb_hcd_pci_probe() called
(drivers\usb\miniport\sys\linuxwrapper.c:201) driver_register 0:
9cf5f0b8 9cf56ec4(drivers\usb\usbport\usb.c:166) INF:
drivers\usb\usbport\usb.c: registered new driver hub
(drivers\usb\miniport\sys\li(drivers\usb\usbport\hub.c:1230) hub_thread
startingnuxwrapper.c:137) usbcore: Created system thread 60
(drivers\usb\miniport\sys\linuxwrapper.c:201) driver_register 1:
9cf5f0e0 9cf56eb0(drivers\usb\usbport\hcd-pci.c:74) usbcore:
usb_hcd_pci_probe() called
(drivers\usb\usbport\/../miniport/linux/pci_hal.c:13)
pci_enable_device() called...
(drivers\usb\usbport\/../miniport/linux/pci_hal.c:44)
pci_resource_flags() called, x=0x0
(drivers\usb\usbport\/../miniport/linux/pci_hal.c:21)
pci_resource_start() called, x=0x0
(drivers\usb\usbport\/../miniport/linux/pci_hal.c:33) pci_resource_len()
called, x=0x0
(drivers\usb\usbport\/../miniport/linux/pci_hal.c:86) request_region():
addr=0x1060, len=0x20
(drivers\usb\usbport\/../miniport/linux/pci_hal.c:58) pci_set_drvdata()
called...
(drivers\usb\usbport\hcd-pci.c:163) UnivHCI PCI-USB Controller
(drivers\usb\usbport\hcd-pci.c:183) irq 9, io base 00001060
(drivers\usb\usbport\hcd.c:678) new USB bus registered, assigned bus
number 1
(drivers\usb\miniport\usbuhci\/../linux/pci_hal.c:33) pci_resource_len()
called, x=0x0
(drivers\usb\miniport\sys\linuxwrapper.c:252) schedule_timeout: 5 ms
(drivers\usb\miniport\sys\linuxwrapper.c:286) schedule DONE!!!!!!
(drivers\usb\miniport\sys\linuxwrapper.c:252) schedule_timeout: 1 ms
(drivers\usb\miniport\sys\linuxwrapper.c:286) schedule DONE!!!!!!
(drivers\usb\miniport\sys\linuxwrapper.c:793) pci_alloc_consistent()
size=8196
(drivers\usb\miniport\sys\linuxwrapper.c:639) pci_pool_create(): UHCD
PCI Slot/uhci_td size 48, 85/page (4096 alloc)
(drivers\usb\miniport\sys\linuxwrapper.c:639) pci_pool_create(): UHCD
PCI Slot/uhci_qh size 48, 85/page (4096 alloc)
(drivers\usb\miniport\usbuhci\uhci-hcd.c:2264) INF:
drivers\usb\miniport\usbuhci\uhci-hcd.c: detected 2 ports
(drivers\usb\usbport\hcd.c:400) root hub device address 1
(drivers\usb\miniport\sys\ros_wrapper.c:8) wait_ms(10)
(drivers\usb\usbport\config.c:274) DBG: drivers\usb\usbport\config.c:
kmalloc IF 8cd05d48, numif 1
(drivers\usb\usbport\usb.c:1215) new device strings: Mfr=3, Product=2,
SerialNumber=1
(drivers\usb\usbport\message.c:1008) DBG: drivers\usb\usbport\message.c:
USB device number 1 default language ID 0x409
(drivers\usb\usbport\usb.c:1051) Product: UnivHCI PCI-USB Controller
(drivers\usb\usbport\usb.c:1059) Manufacturer: XBOX ---- uhci-hcd
(drivers\usb\usbport\usb.c:1086) USB connected: UnivHCI PCI-USB
Controller (XBOX ---- uhci-hcd)
(drivers\usb\usbport\usb-debug.c:184) SerialNumber: UHCD PCI Slot
(drivers\usb\miniport\sys\linuxwrapper.c:167) drv_num 2 9cf56ec4 9cf56eb0
(drivers\usb\usbport\usb.c:1255)
.........................usb_new_device: usb-UHCD PCI Slot-0 interface 0
(drivers\usb\usbport\usb.c:1257) usb_new_device - registering interface
1-0:0
(drivers\usb\miniport\sys\linuxwrapper.c:167) drv_num 2 9cf56ec4 9cf56eb0
(drivers\usb\miniport\sys\linuxwrapper.c:181) probe0 9cf56ec4
(drivers\usb\usbport\usb.c:93) usb_device_probe
(drivers\usb\usbport\usb.c:103) usb_device_probe - got id
(drivers\usb\usbport\hub.c:631) USB hub found
(drivers\usb\usbport\hub.c:390) 2 ports detected
(drivers\usb\usbport\hub.c:405) standalone hub
(drivers\usb\usbport\hub.c:409) ganged power switching
(drivers\usb\usbport\hub.c:422) global over-current protection
(drivers\usb\usbport\hub.c:472) Port indicators are not supported
(drivers\usb\usbport\hub.c:478) power on to power good time: 6ms
(drivers\usb\usbport\hub.c:480) hub controller current requirement: 0mA
(drivers\usb\usbport\hub.c:490) local power source is good
(drivers\usb\usbport\hub.c:493) no over-current condition exists
(drivers\usb\usbport\hub.c:521) hub_thread should woke up
(drivers\usb\usbport\hub.c:309) enabling power on all ports
(drivers\usb\miniport\sys\ros_wrapper.c:8) wait_ms(0)
(drivers\usb\miniport\sys\ros_wrapper.c:8) wait_ms(0)
(drivers\usb\miniport\sys\ros_wrapper.c:8) wait_ms(6)
(drivers\usb\miniport\sys\linuxwrapper.c:181) probe1 9cf56eb0
(drivers\usb\miniport\sys\linuxwrapper.c:201) driver_register 2:
9cf5f268 9cf56ec4(drivers\usb\usbport\usb.c:166) INF:
drivers\usb\usbport\usb.c: registered new driver keyboard
(drivers\usb\miniport\sys\linuxwrapper.c:201) driver_register 3:
9cf5f2e8 9cf56ec4(drivers\usb\usbport\usb.c:166) INF:
drivers\usb\usbport\usb.c: registered new driver usbmouse
Entered debugger on last-chance exception number 14 (Page Fault)
Memory at 0x101c0000 could not be read: Page not present.
kdb:> bt
[7hEip:
<usbuhci.sys:9485 (drivers/usb/miniport/common/misc.c:91
(UsbMpInitMultiSzString))>
Frames:
<usbuhci.sys:98f0 (drivers/usb/miniport/common/pdo.c:112 (UsbMpPdoQueryId))>
<usbuhci.sys:9b15 (drivers/usb/miniport/common/pdo.c:293 (UsbMpPnpPdo))>
<usbuhci.sys:90d9 (drivers/usb/miniport/common/main.c:337 (DispatchPnp))>
<ntoskrnl.exe:425ef (ntoskrnl/io/irp.c:1080 (IofCallDriver))>
<ntoskrnl.exe:45163 (ntoskrnl/io/pnpmgr.c:752 (IopInitiatePnpIrp))>
<ntoskrnl.exe:45e72 (ntoskrnl/io/pnpmgr.c:1398
(IopActionInterrogateDeviceStack))>
<ntoskrnl.exe:451d8 (ntoskrnl/io/pnpmgr.c:782 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4520b (ntoskrnl/io/pnpmgr.c:796 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4524e (ntoskrnl/io/pnpmgr.c:822 (IopTraverseDeviceTree))>
<ntoskrnl.exe:469f2 (ntoskrnl/io/pnpmgr.c:2014
(IopInvalidateDeviceRelations))>
<ntoskrnl.exe:314e6 (ntoskrnl/io/device.c:162 (IopStartDevice))>
<ntoskrnl.exe:46782 (ntoskrnl/io/pnpmgr.c:1831
(IopActionInitChildServices))>
<ntoskrnl.exe:46815 (ntoskrnl/io/pnpmgr.c:1871 (IopActionInitAllServices))>
<ntoskrnl.exe:451d8 (ntoskrnl/io/pnpmgr.c:782 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4520b (ntoskrnl/io/pnpmgr.c:796 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4520b (ntoskrnl/io/pnpmgr.c:796 (IopTraverseDeviceTreeNode))>
<ntoskrnl.exe:4524e (ntoskrnl/io/pnpmgr.c:822 (IopTraverseDeviceTree))>
<ntoskrnl.exe:4687e (ntoskrnl/io/pnpmgr.c:1931 (IopInitializePnpServices))>
<ntoskrnl.exe:c8fe8 (ntoskrnl/io/iomgr.c:421 (IoInit3))>
<ntoskrnl.exe:c6838 (ntoskrnl/ex/init.c:651 (ExpInitializeExecutive))>
<ntoskrnl.exe:6706 (ntoskrnl/ke/main.c:100 (KiSystemStartup))>--- Press
q to abort, any other key to continue ---
<ntoskrnl.exe:c484e (ntoskrnl/ke/main.c:294 (_main))>
<ntoskrnl.exe:104b ({standard input}:47 (_section_alignment__))>
Couldn't access memory at 0x000764f8!
kdb:> regs
CS:EIP 0x0008:0x9cf16485
SS:ESP 0x0010:0x8011a5c0
EAX 0x101c0000 EBX 0x0007651c
ECX 0x0000000c EDX 0x8011a5e8
ESI 0x0007661c EDI 0x00076514
EBP 0x8011a600
EFLAGS 0x00200296 PF AF SF IF IOPL0 ID
kdb:>
Hi,
some compilations failed because strcasecmp is already declared in my
MinGW installation. The work-around was to define HAVE_STRCASECMP in
rosapps/mc/src/util.c (Midnight Commander) and in
reactos/include/wine/config.h.
Regards,
Mark
On Sun, Sep 11, 2005 at 11:07:23AM +0900, Mike McCormack wrote:
>
> Luke Kenneth Casson Leighton wrote:
> >oh maaan, that's really sad: i know what the stuff in subauth.h is all
> >about, aaaaagh!
>
> Looking at the title of the post, I mistakenly thought that you posted a
> patch for a moment...
ha, sorry mike :)
not yet.
many windowisms to learn, which i am hoping to avoid by someone else
picking up the initiative.
i'm focussing on getting samba tng into reasonable shape - compiling
everything under mingw32 is the first step - such that it can be
plugged into an implementation of msv1_0.dll.
however i am not holding out forever waiting for someone else to start
msv1_0.dll.
so i'm trying to track down "LsaAp"s to see if anyone - outside of
microsoft - has ever written one of these.
l.
--
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
okay.
who's the nutcase that's been implementing libsam - i _hope_ you looked
at samba tng's "samrd" source code!!!!
l.
--
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
these are standard smbclient-related and/or rpcclient-related functions.
NetUserGetInfo grabs the information from a NET_USER_INFO_3 structure
which is "cached" from the MSV1_0.DLL access token for example (it's a
really long story).
NetShareEnum() is a LANMAN function, whoopeee what fun.
in nt, there are _stacks_ of functions that tie pretty much
directly into samba source code.
l.
--
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
oh maaan, that's really sad: i know what the stuff in subauth.h is all
about, aaaaagh!
it is incredibly similar to the MSRPC "NETLOGON" stuff that's
implemented in cli_nt_login_interactive, cli_nt_login_network
and cli_nt_login_generic in rpc_client/cli_login.c
joy.
l.
--
--
<a href="http://lkcl.net">http://lkcl.net</a>
--
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>
--