samba - May 2021 - Samba on AIX with security = ads - does it actually work?

On 26/05/2021 16:27, Ben Huntsman wrote:
> >From everything you have posted, I am fairly convinced that you have an
> >AIX problem and not a Samba problem. I can assure you that Samba works
> >on Linux, it just doesn't seem to work on AIX.
>
> I concur. ?I never suggested there was any problem on Linux, it's just 
> not a Linux server we need this working on. ?I was hoping that maybe 
> we could gather enough info that a bug could be identified and perhaps 
> fixed...
>
> Thanks again!
>
> -Ben
>
I have just found this: 
https://unix.stackexchange.com/questions/553943/aix-and-winbind-users-works-fine-all-except-fori-have-no-name


Which seems to say that whilst AIX is a 64bit OS, Samba for some 
inexplicable reason is 32bit and so lsuser doesn't work. I have no idea 
if this is true, but it is worth checking and if it is true, then you 
need to speak to whomever is compiling Samba.


Rowland

>Which seems to say that whilst AIX is a 64bit OS, Samba for some
>inexplicable reason is 32bit and so lsuser doesn't work. I have no idea
>if this is true, but it is worth checking and if it is true, then you
>need to speak to whomever is compiling Samba.
That may or may not be a red herring.  id_32 and id_64 are not native AIX
utilities, but are provided by coreutils.  On my system, the native AIX id
command returns data for AD users when winbind is configured.  Interestingly,
id_32 returns data also, but more of it.  id_64 indeed says "no such
user".  But again, the AIX id command does so I would think it'd be
good to go.

You are right though that Samba is built as 32-bit on AIX:

# dump -ov /opt/freeware/lib/WINBIND.so

/opt/freeware/lib/WINBIND.so:

                        ***Object Module Header***
# Sections      Symbol Ptr      # Symbols       Opt Hdr Len     Flags
         4      0x00005098            353                72     0x3002
Flags=( EXEC DYNLOAD SHROBJ DEP_SYSTEM )
Timestamp = "Feb 09 08:27:01 2021"
Magic = 0x1df  (32-bit XCOFF)

                        ***Optional Header***
Tsize       Dsize       Bsize       Tstart      Dstart
0x000038df  0x000001a9  0x00000008  0x10000128  0x30000a07

SNloader    SNentry     SNtext      SNtoc       SNdata
0x0004      0x0002      0x0001      0x0002      0x0002

TXTalign    DATAalign   TOC         vstamp      entry
0x0007      0x0002      0x30000b10  0x0001      0x30000a18

maxSTACK    maxDATA     SNbss       magic       modtype
0x00000000  0x80000000  0x0003      0x010b        RE


That being the case, I would think we'd want to have a WINBIND.so in
/opt/freeware/lib64 as well. Any way to force a 64-bit (or both simultaneously)
build?  In this case it was IBM who did the compile.

But regardless, I'm not sure if it matters for the specific error in
question...

Thanks again!

-Ben