samba - Jun 2018 - Building rpcclient statically linked?

On Mon, Jun 18, 2018 at 3:53 PM, pisymbol <pisymbol at gmail.com> wrote:
>
>
> On Mon, Jun 18, 2018 at 2:39 PM, Andrew Bartlett <abartlet at
samba.org>
> wrote:
>
>> On Mon, 2018-06-18 at 10:35 -0400, pisymbol via samba wrote:
>> > Small addendum, I did try:
>> >
>> > ./configure --nonshared-binary=ALL
>> >
>> > ERROR: source source3/smbd/notify_msg.c is in more than one
subsystem of
>> > target 'smbstatus': ['smbd_base.objlist',
'smbstatus.objlist']
>> >
>> > This is CentOS 7.5.
>> >
>> > -aps
>>
>> Building more than smbd and smbtorture nonshared is simply not tested.
>>
>> The configure incantation for those is --nonshared-
>> binary=smbtorture,smbd/smbd
>>
>
>
> This is what I feared!
>
>
>>
>> You can try --nonshared-binary=rpcclient but I suspect it will fail
>> similarly, because so far nobody has done the work to ensure that each
>> C file is only in one subsystem.
>>
>> Now, you have actually identified a bug, for smbstatus notify_msg.c is
>> listed twice in the wscript_build file.  Ideally Samba (or at least
>> larger parts of Samba) would build as you suggest because it does
>> identify real-world issues.  While this file has no static data, if a C
>>
>> file is linked in twice with static data the results can be un-desired.
>>
>
> Totally understood. I figured it was a bug but I'm not a waf expert to
be
> confident in that assessment.
>
>
>>
>> From here however you can only try, and work to break up our dependency
>> list into a directed acyclic graph.  This is harder than is looks!
>>
>> Finally, perhaps you could detail what you are hoping to achieve with a
>> static rpcclient?  We may have another way to assist you with your
>> aims.
>>
>
> Andrew, very simply, I need a way to dump the raw share ACL.
>
> Currently, I have a modified version of rpcclient that issues an info
> level 502 request but instead of parsing the share
> security descriptor for rpcclient to parse, it copies the SD as a raw
> binary buffer that I can print to stdout for another tool
> to pickup and store for offline purposes.
>
Eee gad. What I meant was:

I have a binary based off of rpclient that prints out the raw share SD as a
binary stream instead of trying to parse it into human readable format (the
default behavior). That is what I'm after.

Hopefully that makes more sense.

Cheers!

-aps

On Mon, 2018-06-18 at 15:56 -0400, pisymbol wrote:
> I have a binary based off of rpclient that prints out the raw share
> SD as a binary stream instead of trying to parse it into human
> readable format (the default behavior). That is what I'm after.
> 
> Hopefully that makes more sense.
Personally I would do that with our python bindings.

Andrew Bartlett

-- 
Andrew Bartlett                       http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT          http://catalyst.net.nz/services/samba

On Mon, Jun 18, 2018 at 11:36 PM, Andrew Bartlett <abartlet at samba.org>
wrote:
> On Mon, 2018-06-18 at 15:56 -0400, pisymbol wrote:
> > I have a binary based off of rpclient that prints out the raw share
> > SD as a binary stream instead of trying to parse it into human
> > readable format (the default behavior). That is what I'm after.
> >
> > Hopefully that makes more sense.
>
> Personally I would do that with our python bindings.
>
>
Can you elaborate a bit more? If the python bindings are well, just that,
aren't they subject to the same limitations as the rpcclient binary itself,
i.e. gen_ndr et al not copying out the raw SD?

Or are you saying there is a way for me to send the underlying RPC itself
to bypass all of this stuff like rpcclient does via the bindings?

i would be thrilled to get the Python stuff working. I once looked into
this about a year or so ago but there wan't any documentation and I think
the whole Python bindings stuff was still in flux at the time.

-aps