[Samba] Samba client 3.6.5 fails sending to MAC 0S 10.9.x Maverick server
Michael.Tompkins at xerox.com
Thu Oct 30 05:37:17 MDT 2014
We did not back port SMB2 support for the client to 3.6.5. There was too much refactoring done from 3.x to 4.x, so we chose to start supporting SMB2 with the 4.0.7 release. And the SMB2 functionality was not supported by samba until 4.1.x, so we backported the SMB2 from 4.1 to 4.0.7, per Jeremy's SMB2 patch. And the only reason we chose that, instead trying to keep up with the latest 4.1.x, is we could never get the cross compiling to work with WAF. So, we would like a solution for our customers with the legacy 3.6.5 smbclient. This must have been an issue before with other 3.x clients, to the MAC OS 10.9.x, so we're hoping someone can provide us with a solution.
From: Jeremy Allison [mailto:jra at samba.org]
Sent: Wednesday, October 29, 2014 11:24 PM
To: Tompkins, Michael
Cc: samba at lists.samba.org; USA Xerox Samba; Faynor, John
Subject: Re: [Samba] Samba client 3.6.5 fails sending to MAC 0S 10.9.x Maverick server
On Wed, Oct 29, 2014 at 06:23:26PM +0000, Tompkins, Michael wrote:
> I have been searching for weeks for information to our problem, trying to connect our smbclient 3.6.5 to a MAC running 10.9.5 server, and I finally came across the reason. It appears with Maverick, Apple will only accept SMB2 signed signatures. The problem with the 3.6.5 client is, it never supported SMB2, thus will not write the SMB2 signatures. I can add "client signing = disabled" to the smb.conf file, but I don't want to restrict for all servers, a device may talk to. Is there any workaround for 3.6.5, so I can be flexible depending on the server ? Any help would be appreciated, even from Apple if anyone has a contact. I've tried several, but have not received a response.
The 4.1.x client fully supports SMB2 signatures.
Did you back-port all the client code to 3.6.5 ?
You might want to extend the back-port to include the SMB2 client signing.
More information about the samba