Update SMB library to fix issues with Windows 7

[GoogleCodeExporter]

Honestly, I have no idea if this is an issue with atvusb-creator or XBMC, but I 
figured I'd start here first.

On Windows 7 many installs come equipped with a program called Windows Live ID 
Sign-On Assistant. Having this program installed 100% breaks SMB shares in XBMC 
(and presumably Boxee and other programs as well) on the Apple TV.

The problem is detailed on the Samba bug tracker, here:
https://bugzilla.samba.org/show_bug.cgi?id=7577

Here's someone with the bug on the XBMC forums:
http://forum.xbmc.org/showthread.php?t=54605

As of right now, the program in question does absolutely nothing useful and can 
be uninstalled. The issue is totally resolved by uninstalling the program. 
Success! However, Microsoft is currently undertaking steps to make the program 
mandatory. Starting on November 15th, it will be impossible to play games on 
Microsoft's GFWL service without the client installed. This is the first step; 
in the future all MS Live programs including Messenger and Mail will presumably 
require this service.

The good news is that the bug has already been fixed as per that Samba.org bug 
listing, you just need to update your samba client. 

So, how do we go about getting this fixed on the Apple TV? Do we manually 
update Samba? I understand that Samba on the Apple TV uses some Mac kernel 
extension from 10.4, so would it be necessary for Apple to update that kernel 
extension for the solution to work on the Apple TV? Is there anything we can do 
or you can do to update Samba in such a way that solves this problem?

Thanks in advance.

Original issue reported on code.google.com by stumpoka...@gmail.com on 7 Nov 2010 at 2:53

[GoogleCodeExporter]

xbmc uses an internal smbclient, this would have to be updated or patched. 

Original comment by sdavi...@gmail.com on 7 Nov 2010 at 4:18

[GoogleCodeExporter]

Okay, so, I went to the XBMC forums and over there I have Team-XBMC developer 
elupus telling me that XBMC does not roll their own smbclient, it uses the 
operating system's smbclient.

Checking online, it looks like the XBMC4Xbox fork uses their own smbclient and 
the Apple TV fork seems to be the same way; when I SSH'd into my Apple TV and 
used find to find any files with smb in the filename, the only library was 
inside /Applications/XBMC.Apps/Frameworks/.

I can't tell if you're right or they're right, but honestly I don't really 
care. I just know that this is becoming an increasingly big problem, by next 
year or the year after Microsoft will have made WLISA mandatory for all of 
their Live-enabled programs at which point XBMC on AppleTV will effectively be 
broken for all Windows 7 users, and the fix seems trivial; simply update the 
version of libsmb.

Even if this isn't a problem with the atvusb-creator / Downloader, even if this 
is a problem with XBMC, do you have any suggestions how I can get a new copy of 
libsmb onto my AppleTV? What should I do?

Original comment by stumpoka...@gmail.com on 22 Nov 2010 at 5:31

[GoogleCodeExporter]

Team-XBMC developer, replying to me being confused about the fact that you've 
told me XBMC uses their own internal smb client, and Team-XBMC developer elupus 
telling me that they don't, said "who are you gonna trust? the xbmc devs or 
some random third party?"

Original comment by stumpoka...@gmail.com on 22 Nov 2010 at 5:49

[GoogleCodeExporter]

Take your bitching to microsoft, they caused this issue. It's not a simple 
issue to "just update" libsmbclient. There's much more involved with it. A fix 
is planned but I'm not jumping through hoops just for this. Disable WLISA and 
file a complaint with Microsoft. 

Original comment by sdavi...@gmail.com on 22 Nov 2010 at 5:58

[GoogleCodeExporter]

I think that's a pretty negative attitude to have towards this issue. 

First, you know full well that Microsoft isn't going to do anything. I'm not a 
big Microsoft fan either. More to the point, it's a problem that's increasing 
as Microsoft begins to bundle the sign-in assistant with more and more software 
(including an OEM install of Windows 7 that I helped a friend with a few weeks 
ago), and it's now mandatory with their gaming initiative. There are users on 
XBMC's forums pointing out that they need to choose between being able to play 
the games they've purchased or being able to watch their media content.

Second, when a user approached the Samba programmers with the issue, they 
worked to fix it. When a user approached the XBMC4Xbox people, they worked to 
fix it. I'm sure both of those groups thought it was ridiculous that Microsoft 
caused the issue, but the worked to fix it. In both those cases, the fix came 
relatively quickly. If I seemed flippant to how much work the fix would be, it 
was because all the investigation I did suggested it was a minor fix.

I understand that it's hard work and I appreciate all the effort, but you don't 
need to be dismissive. I don't feel like I'm bitching. This is an issue 
tracker. This is an issue either with ATVusbcreator or XBMC; I asked politely 
here and then asked politely over there. I made an effort to do as much legwork 
as I could to find the source of the problem and the suggested solution. I 
didn't wander in with a poorly defined problem like most users do or would.

Third, if I do sound frustrated, it's because I filed this issue here, you said 
that it was an XBMC issue, I filed the issue there, they said it was an AppleTV 
issue. I understand that I don't pay for your software and you might feel 
frustrated that some users seem entitled. I'm sorry if I seem entitled.

Original comment by stumpoka...@gmail.com on 22 Nov 2010 at 6:15

[GoogleCodeExporter]

Look, microsoft made a nasty change with complete disregard for everything out 
there that uses SMB. Typical Microsoft attitude. Now we get to disrupt our 
planned schedule to jump over hoops to fix this mess. Some XBMC platforms 
(Linux), it's up to distros to provide the fix. On others (XBMC for Mac/ATV), 
there's a way to fix it and there's a way not to fix it. That's under 
investigation. What I won't do is drop everything I currently doing and rush to 
fix this without considering the ramifications. We have a release brewing and I 
can't just slam in a fix without proper testing that ensure that what gets 
released does not cause other problems. 

Now dealing with answering this issue on forums and here has sucked away 1/2 
hour of my time, taken my focus away from what I doing and generally disrupted 
the rest of my day. I'm not happy about this.

Original comment by sdavi...@gmail.com on 22 Nov 2010 at 6:53