search for: latest_new

On Thu, 19 Jul 2018 09:28:41 -0300 Elias Pereira via samba <samba at lists.samba.org> wrote: > Wow!!!! > > I'm happy to read this !!! Thank you for your excellent work Louis !!! > > Do you already have 4.8.3 in production? > > Do you have any idea to put in your apt the 4.9 version? :D > Give him a chance, 4.9.0 has not been released yet ;-) Rowland

On Thu, 19 Jul 2018 09:49:33 -0300 Elias Pereira via samba <samba at lists.samba.org> wrote: > > > > Give him a chance, 4.9.0 has not been released yet ;-) > > > Released not yet, but available for Download!! :) > > https://www.samba.org/samba/latest_news.html#4.9.0rc1 > https://www.spinics.net/lists/samba/msg150987.html > Did you miss the 'rc1' bit on the end ? It isn't ready for production yet, it should only be used for testing. Rowland

Hi all, A - I thought badlock mitigation was about encrypting SMB traffic, at least most part of it. And this encryption of most part of data transfer could (or should) lower performances. It seems I was wrong: smallest part (something like commands) are encrypted but not SMB traffic (ie file transfer). This for SMB protocol prior to SMB3 (which comes with windows 8). B - According to what I

I was looking at https://www.samba.org/samba/latest_news.html#4.4.2 and added server signing = mandatory ntlm auth = no to smb.conf but that seems to have made it worse. Before adding that I was still able to do wbinfo -g and get a group listing Is there settings to set it back to the untrusted way before the security updates that happened? I'...

...(which comes with windows 8). >> B - According to what I read, new options added into smb.conf with Samba versions meant to solve Badlock >> issue are enough by default to solve the issue. If I understood you correctly, your questions are answered here: https://www.samba.org/samba/latest_news.html "It is recommended that administrators set these additional options, if compatible with their network environment: server signing = mandatory ntlm auth = no Without "server signing = mandatory", man in the Middle attacks are still possible against our file server and class...

In case anyone has been wondering what we get up to in the Samba project, here's a blog post on the last month or so of conference and Samba activity. Enjoy ! https://www.samba.org/samba/latest_news.html#sdc_ms_trip Jeremy. PS. Samba on Windows ! w00t! :-).

...6, pid=19397, effective(0, 0), real(0, 0), class=winbind] ../source3/winbindd/winbindd.c:965(winbind_client_request_read) closing socket 28, client exited On Wed, Apr 20, 2016 at 8:05 AM, Jeff Sadowski <jeff.sadowski at gmail.com> wrote: > I was looking at https://www.samba.org/samba/latest_news.html#4.4.2 > > and added > > server signing = mandatory > ntlm auth = no > > to smb.conf but that seems to have made it worse. Before adding that I was > still able to do wbinfo -g and get a group listing > > Is there settings to set it back to the untrusted way bef...

Hello, I have a Centos 7 system running samba that is joined to an ADS. When I was running 4.4.0 everything worked just fine. When I installed 4.4.2 samba stopped authenticating passwords against the ads properly. I am using sssd and have verified that it is working correctly and able to validate passwords. I am not running winbind. Both 4.4.0 and 4.4.2 were compiled using exactly the same

When ubuntu 14.04 went from samba 4.1.6 to 4.3.8 it killed my setup. Before the change I was able to run wbinfo -u and get a list of users. Now when I run wbinfo -u it returns nothing. I tried dis-joining and rejoining the domain with no luck, Here is my complete smb.conf [global] security = ads realm = SUBDOMAIN.DOMAIN.TOP workgroup = SUBDOMAIN idmap config * : backend = tdb idmap config * :

Hi, I have Samba 4.2.10 server with NT4 configuration, with ldap backend on Debian Jessie, and I want to upgrade it to AD. I test it now in virtul environment. The classicupgrade was succesful. getent passwd username and chown "username:Domain Users" test.txt didn't work with this nsswitch.conf: passwd: files ldap group: files ldap shadow: files ldap , so I changed ldap to winbind.