[Samba] Info/Feedback on Samba bug #8744...

Rowland Penny rowlandpenny at googlemail.com
Mon Jan 5 09:24:31 MST 2015

On 05/01/15 16:16, Marco Gaiarin wrote:
> Mandi! L.P.H. van Belle
>    In chel di` si favelave...
>> Im not into radius (yet)... but you can try upgrading samba.
>> echo "# Backports repository" >> /etc/apt/sources.list.d/debian-backport.list
>> echo "deb http://ftp.nl.debian.org/debian/ wheezy-backports main " >> /etc/apt/sources.list.d/debian-backport.list
>> apt-get update && apt-get upgrade
>> and try again.
> Switching to backports meant switching also to samba4:
> 	https://packages.debian.org/wheezy-backports/samba
> and for now i prefere to remain on samba3, i'm still on the process to
> evaluate the move to samba4.
> So, i hope the bug (not present on samba 3.5!!!) will be identified and
> fixed...

Not much chance of that, 3.6 is in security fixes only at the moment and 
when 4.2 comes out, it will go EOL. Samba 4.2.rc3 was released on the 
20th Dec 2014, so as you can see, 4.2 is very imminent. Louis's advise 
is the way to go, if the problem is still there you should be able to 
get it fixed, but then again, it may already be fixed in 4.1.9 from 


More information about the samba mailing list