smbclient 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse name from info level 260

Bug #1576449 reported by Jeremy Null
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
samba (Debian)
Fix Released
Unknown
samba (Ubuntu)
Fix Released
High
Ubuntu Security Team

Bug Description

Using Ubuntu 14.04.4 LTS (GNU/Linux 3.13.0-85-generic x86_64)
Samba package 4.3.8-Ubuntu gives you the error...

cli_list: Error: unable to parse name from info level 260
NT_STATUS_NO_MEMORY listing \*

...When you try to ls a Windows 10 machine.

the Samba team has a bug file/patch for it here:
https://bugzilla.samba.org/show_bug.cgi?id=11822
and here:
https://bugzilla.samba.org/show_bug.cgi?id=11831

affects: ubuntu → samba (Ubuntu)
summary: - 4.3.8-Ubuntu cli_list: Error: unable to parse name from info level 260
+ 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse name from
+ info level 260
summary: - 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse name from
- info level 260
+ Samba 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse name
+ from info level 260
Revision history for this message
Sebastien Bacher (seb128) wrote : Re: Samba 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse name from info level 260

Thank you for your bug report and for pointing to the upstream bug/patch. Is that a regression from the 4.3 security update? (assigning to the security team under that understanding, but if that's not one it should probably be handled as a normal SRU instead)

Changed in samba (Ubuntu):
assignee: nobody → Ubuntu Security Team (ubuntu-security)
importance: Undecided → High
Revision history for this message
Jeremy Null (soteriologist) wrote :

No, it's post/aside-from the 4.3 security update. It happened both before/and after the update. Plus, I believe their patch is for any 4.3.x and 4.4.x versions. Double check me on that though.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Today's Samba update should contain the fix for this issue, could the original bug reporter please test the update and comment here?

http://www.ubuntu.com/usn/usn-2950-2/

Revision history for this message
Jeremy Null (soteriologist) wrote :

This fixed it! Samba is connecting great again to my Windows 10 machines and they're all backing up now. Thank you!

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Great, I'm closing this bug. Thanks!

Changed in samba (Ubuntu):
status: New → Fix Released
Axel Beckert (xtaran)
summary: - Samba 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse name
- from info level 260
+ smblcient 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse
+ name from info level 260
summary: - smblcient 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse
+ smbclient 4.3.8-Ubuntu ls Windows 10 cli_list: Error: unable to parse
name from info level 260
Changed in samba (Debian):
status: Unknown → New
Changed in samba (Debian):
status: New → Confirmed
Changed in samba (Debian):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.