building source3 subsystems and libs

[moore chestnut]

hello Andrew:

regarding why:
- initially because I'm finding my way around this code base and I dont
know all the options... :-)
- I want a simplified, lean client that I have can use for testing and
understanding.
- a starting point i was looking at was the rpc_open_tcp and then try build
on that with the functionality in netlogon_creds_cli.c for a ntlm pass
thru, but even that has lots of dependencies.

otherwise, as an end goal, this might be something that I want to use in an
extremely constrained embedded environment.
so having full samba build/deployment is not going to be an option.
the list of dependencies and nested dependencies is long so I want to
determine if a streamlined client is possible.

rpcclient bin itself is fully loaded with dependencies and even a test with
NETLOGON command uses lsarpc, over dcerpc over smb over tcp.
Of course there is high chance I'm misunderstanding and based on what I
think I need around dcerpc bind, epm mapper, schannel netrlogonsamlogon for
ntlm pass thru.

your thoughts appreciated.

thank you.


On Thu, 21 Nov 2019 at 23:07, Andrew Bartlett <abartlet at samba.org> wrote:

> Is there a reason why you first want to untangle our build system?
>
> I would suggest first just creating a new binary, which links against
> whatever it needs to (and we have great helper libraries for the things
> you need for the below).
>
> rpcclient has a samlogon command that does what you need, I would just
> cut that down.
>
> But why not just use winbind via ntlm_auth or libwbclient?  That has
> everything setup and ready to go, manages the connection and
> everything.
>
> Perhaps it would help to explain your use case first.
>
> Thanks!
>
> Andrew Bartlett
>
> On Thu, 2019-11-21 at 22:52 +0000, moore chestnut wrote:
> > Hello Andrew,
> >
> > thank you for reply.
> >
> > so would it be bad a idea to try hack a build together based on the
> > source files of msrpc3 and the deps?
> >
> > essentially I would like to hack a client together to do dcerpc bind,
> > epm mapper request, followed by bind and schannel setup (
> > NetrServerReqChallenge and NetRServerReqAuthenticate3) followed by
> > bind and NetrLogonSamLogonWithFlags.
> >
> > Any suggestions on best approach?
> >
> >
> >
> >
> >
> >
> >
> > On Thu, 21 Nov 2019 at 18:18, Andrew Bartlett <abartlet at samba.org>
> > wrote:
> > > On Thu, 2019-11-21 at 18:09 +0000, moore chestnut via samba-
> > > technical
> > > wrote:
> > > >   hello,
> > > >
> > > > is there any way to individually build subsystems and libraries?
> > > >
> > > > for example:
> > > >
> > > > the msrpc3 library in  source3/wscript_build
> > > > bld.SAMBA3_LIBRARY('msrpc3',
> > > >
> > > > or
> > > > bld.SAMBA3_SUBSYSTEM('samba3util',
> > > >
> > > > when I try waf or waf msrpc3 in the source3 dir, it does not
> > > work.
> > > >
> > > > currently trying on a 4.11.0 source tree.
> > > >
> > > > I have read through the https://wiki.samba.org/index.php/Waf
> > > > and tried the samples with no success.
> > > >
> > > > Does this work for source3 libs/subsystems?
> > >
> > > No, you can't really build bits of Samba in general.  Some binary
> > > targets can be specified with the --targets option, and a few of
> > > these
> > > work correctly, nothing beyond that has been tested.  So where it
> > > works
> > > it works, but nobody is really working to have this be a general
> > > feature.
> > >
> > > Andrew Bartlett
> > >
> --
> Andrew Bartlett
> https://samba.org/~abartlet/
> Authentication Developer, Samba Team         https://samba.org
> Samba Development and Support, Catalyst IT
> https://catalyst.net.nz/services/samba
>
>
>
>
>
>