[Samba] protocol between pam/nss & winbindd

[Rowland Penny]

On Wed, 2022-06-01 at 12:40 +0300, Michael Tokarev wrote:
> 01.06.2022 12:35, Rowland Penny via samba wrote:
> > On Wed, 2022-06-01 at 12:11 +0300, Michael Tokarev via samba wrote:
> > > Hi!
> > > 
> > > Is the (local) protocol between pam_winbind, nss_winbind
> > > and winbindd architecture-agnostic, like, using network
> > > types and network byte order, or is it architecture-dependent?
> > > 
> > > I mean, for example, on a bi-arch machine (i386 & x86_64), will
> > > single winbindd serve both 32 and 64 bit clients fine?
> > > 
> > > Will it work if I run, say, armhf binary with armhf nss_winbind
> > > on the same machine with qemu-user-arm emulation, - will x86_64
> > > winbindd understand armhf client and reply to it correctly?
> > 
> > I take it that you mean, will a Linux x86_64 client work against a
> > Samba AD DC running on something like an rpi (or the other way
> > around),
> > if so, then yes, it works.
> 
> I think it should be clear from both the subject and the body of my
> message that I'm talking entirely about a different thing.

No it wasn't, not to me anyway, but after taking that into account
about what you are asking and rereading  your post, it sounds like you
mean either: 
Can you install armhf packages on x86_64, which I am sure you know is
'no' 

Or

Will a virtual machine running armhf talk to the base machine running
x86_64, in which case the answer is what I said previously, 'yes'

If you mean something else, please clearly state what this is.

Rowland