We should provide backports for the patches that recently landed in master which fix the OS X client remote arch detection.
This can useful for employing a server side workaround for bug #11596
Will attach backports once I have this bugs bug id.
Created attachment 11897 [details]
Patch for 4.3 cherry-picked from master
Created attachment 11898 [details]
Patch for 4.4 cherry-picked from master
Created attachment 11899 [details]
Patch for 4.2 backported from master
Re-assigning to Karolin for inclusion in 4.4.0, 4.3.next, 4.2.next.
(In reply to Jeremy Allison from comment #4)
Pushed to autobuild-v4-[4|3|2]-test.
FWIW, the remote arch detection for OS X works well on initial connect, but if the smbd services are restarted on the server and OS X clients reconnect they are not identified as OSX.
I was informed that this was due to the client doing a direct SMB2 negprot instead of a SMB1 negprot where the fingerprinting happens.
So this is helpful as a best-effort tool for debugging, but not as a reliable way to configure smbd.
(In reply to Karolin Seeger from comment #5)
Pushed to all branches.
Closing out bug report.
reopening this bug because:
(1) the man page needs to be adopted also
(2) I think comment #6 is an important point - Ralph do you see a way to make the detection work also for reconnecting clients?
ahm, for the man page, OSX we had that already documented for %a.
For the reconnecting clients the problem is more difficult, as the SMB2 negprot of the reconnecting clients does not contain the protocols that we use to fingerprint the client OS. We might put the result of the SMB1 negprog arch detection into a cache though and use the cached result when a SMB2 negprog comes in. This *might* be a way to fix reconnecting clients.
This is addressed by the patch series git log -4 a2c59d3e45e71b44d9135b35c1cf5522e04dec0e in master. The patches are also in 4.5, but not in older versions.
Closing as fixed.