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>
--
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>
--