similar to: [Announce] Samba 4.6.8, 4.5.14 and 4.4.16 Security Releases Available

Hi Team, Workaround for CVE-2017-12151 :- client max protocol = NT1 and CVE-2017-12163 :- server min protocol = SMB2_02 are contradicting to each other. CVE-2017-12151 impacts on SMB3 protocol but workaound suggst to use NT1. I have below queries regarding this. Is SMB2 protocol also impacted by CVE-2017-12151 ? Can i use client max protocol = SMB2 so that it does not contradict with

On 9/21/2017 5:25 AM, Karolin Seeger via samba wrote: > ====================================================== > "Debugging is like being the detective > in a crime movie where you are also > the murderer." > > Filipe Fortes > ====================================================== > > > Release Announcements > --------------------- > >

====================================================== "Everyone responds to kindness." Richard Gere ====================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.5 release series. Changes since 4.5.12: --------------------- o Jeremy Allison <jra at samba.org> * BUG

====================================================== "Everyone responds to kindness." Richard Gere ====================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.5 release series. Changes since 4.5.12: --------------------- o Jeremy Allison <jra at samba.org> * BUG

====================================================== "Debugging is like being the detective in a crime movie where you are also the murderer." Filipe Fortes ====================================================== Release Announcements --------------------- This is the first stable release of Samba 4.7. Please read the release notes carefully before upgrading. UPGRADING

====================================================== "Debugging is like being the detective in a crime movie where you are also the murderer." Filipe Fortes ====================================================== Release Announcements --------------------- This is the first stable release of Samba 4.7. Please read the release notes carefully before upgrading. UPGRADING

====================================================== "Horses lend us the wings we lack." Pam Brown ====================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.6 release series. Changes since 4.6.6: --------------------- o Jeremy Allison <jra at samba.org> * BUG 12836: s3: smbd:

====================================================== "Horses lend us the wings we lack." Pam Brown ====================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.6 release series. Changes since 4.6.6: --------------------- o Jeremy Allison <jra at samba.org> * BUG 12836: s3: smbd:

Release Announcements ===================== This is the third release candidate of Samba 4.7. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.7 will be the next version of the Samba suite. UPGRADING ========= smbclient changes -----------------

Release Announcements ===================== This is the fourth release candidate of Samba 4.7. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.7 will be the next version of the Samba suite. UPGRADING ========= smbclient changes -----------------

Release Announcements ===================== This is the fourth release candidate of Samba 4.7. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.7 will be the next version of the Samba suite. UPGRADING ========= smbclient changes -----------------

Release Announcements ===================== This is the fifth release candidate of Samba 4.7. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.7 will be the next version of the Samba suite. UPGRADING ========= 'smbclient' changes

Release Announcements ===================== This is the fifth release candidate of Samba 4.7. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.7 will be the next version of the Samba suite. UPGRADING ========= 'smbclient' changes

Release Announcements ===================== This is the sixth release candidate of Samba 4.7. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.7 will be the next version of the Samba suite. UPGRADING ========= 'smbclient' changes

Release Announcements ===================== This is the sixth release candidate of Samba 4.7. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.7 will be the next version of the Samba suite. UPGRADING ========= 'smbclient' changes

Hai,   I've updated the packages on my repo. Please take note of the following.   Jessie-backports ( waiting on fixed debian version ) Jessie 4.5.12 ->  4.5.14 Jessie (unstable) 4.6.7 -> 4.6.8 Stretch-backports ( waiting on fixed debian version ) Stretch 4.6.7 -> 4.6.8 Stretch-unstable ( waiting for 4.7 )   I made a small change in the source and package names. You guys will not

Mason, You can set these also on the share. Win7 and10 client min protocol = SMB2 client max protocol = SMB3 The one for the scanner, client min protocol = NT1 client max protocol = SMB2 Part of my smbstatus -a: PID Username Group Machine Protocol Version Encryption Signing 27316 root root

I have a classic NT4 domain with the PDC also the wins server. With the recent ransomware problem, we're trying to remove SMB1 and below protocols. However when I do this, the browse list is gone. Hosts can access properly the shares, but they have to know exactly \\machine\share in order to to connect. The same thing from a linux client: smbclient -L {PDC} -m SMB2 Domain=[{MYDOMAIN}]

Release Announcements ===================== This is the fourth release candidate of Samba 4.1. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.1 will be the next version of the Samba suite and includes all the technology found in both the Samba4

Release Announcements ===================== This is the fourth release candidate of Samba 4.1. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.1 will be the next version of the Samba suite and includes all the technology found in both the Samba4