Microsoft Working For Samba Interoperability
JP writes "Andrew Bartlett of Samba fame has written a document describing their recent collaboration with Microsoft's Active Directory team. In brief, it would seem that the sky is falling, as Microsoft's engineers seem to be really committed to making Samba fully interoperable with AD. They have organized interoperability fests and have knowledgeable engineers answering technical questions without legal or marketing drones getting in the way. However according to Andrew the Samba AD team is currently very short on manpower, so if you have network experience, now is the time to get coding."
and this will probably be of some benefit to Microsoft, since playing well with other operating systems must always be an advantage.
i find your lack of faith in science disturbing!
I could probably make some small contribution but have neither the time nor inclination to set up the dev and test environment.
For projects of this magnitude a site that could be ssh'd to, 'check out' a dev environment slice would make it a whole lot more practical for folks to work on a small bug or enhancement.
Seems like a good time for some of the larger distros to help Samba out.
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
You seem to not read carefully the most important part: "Microsoft's engineers seem to be really committed to making Samba fully interoperable with AD"
M$ engineers are normal folks like you and me. Well, probably not me. The all cr*p breaks loose when M$ management gets involved and start pushing its political agendas.
If cooperation between AD and Samba folks would be successful, rest assured some M$ managers would try to stick themselves into the project to get a free share of credit for the success.
All hope abandon ye who enter here.
If MS is truly working with Samba to get it 100 percent, what I'd REALLY like to see (and I won't believe they ARE working with SMB until then) is non-encrypted passwords.
SHARE the SMB password system, make it available, so not every friggin windows machine has to do unencrypted passwords across the network to access SAMBA shares / printers / whatever.
That's always been my BIGGEST stumbling block. Linux is touted as being so secure, but then it has to use unencrypted passwords to chat with the desktop clients for sharing.
I KNOW it's an MS problem (their authentications schemas are proprietary), but if they claim to be trying for interoperability (which, they probably are), this was / is my biggest hurdle to accepting *nix in a windows shop.
--Toll_Free
I work for a company that does a lot of integration for enterprise customers. Sometimes there are spaces for Microsoft products in an otherwise Unix environment. Our customers happen to be pretty set on using Unix in general, so for Microsoft, it makes sense to make sure that their products can fit into an environment like that without any hassle. After all, a small sale is better than no sale.
Due to NDA's, MS Engineers are probably not being helpful without management.
Whether or not management CONTINUES to allow them to be helpful, remains to be seen.
You DID bring up a good point, though.
--Toll_Free
... and then claim patent or copyright infringement.
I am officially gone from
I cannot believe the samba team is down to ONE full time developer.
Its a HUGE project to undertake.
When I buy my Red Hat, Suse or Ubuntu thingies for money, Im thinking some of that money goes to helping FOSS developers.
Hey, it better be that way guys: put some dough into Samba.... NOW!
NO SIG
Its already interoperable, but the MS AD team isn't going to stop adding features just because its going to break the desktops of people who don't pay them. But if they break things too much, they get sued to death over their monopoly. Their only solution is to make sure the Samba project keeps up, so its what they do.
Wouldn't this be a GOOD time to have legal drones getting involved? No, not Microsoft's lawyers, the ones that will protect the interests of the Samba intellectual property?
I'm not suprised.
For a long time Microsoft has had a package called Services For Unix that you can install on Windows. It allows Windows to act as a server but not a client with respect to standard *nix protocols like NFS.
Microsoft wants to replace *nix in the server space by breaking into purely *nix environments and replacing an entrenched server operating system with their operating system.
Whether this is done by making Windows interoperable with the protocols that are already on the clients or changing the clients to interoperate with Windows as a server is immaterial.
Unless they're making it easy for people to replace Windows AD servers with Samba servers running on Linux, this is not a big deal.
MS will release Open Source AD compatible Samba - which everyone will use and will come with some weird license that everyone will argue with and MS will simply wipe out all products that use the MS AD Samba.
Embrace, extend, extinguish.
How hard is this to understand?
Here will be an old abusing of God's patience and the king's English.