similar to: [Announce] Samba 4.11.12 Available for Download

Hai, The latest update is now online for Debian Buster Samba 4.11.12 (amd64/i386/armhf) The Changelog, mostly the samba log, last 2 lines are my added changes for the packaging. No big changes. samba (2:4.11.12+dfsg-0.1buster1) buster; urgency=medium . * Non-maintainer upload. * New upstream release builded from samba.org sources. * Bugfix release, fixes bugzilla bugnummers:

Release Announcements --------------------- This is the latest stable release of the Samba 4.12 release series. Changes since 4.12.5 -------------------- o Jeremy Allison <jra at samba.org> * BUG 14403: s3: libsmb: Fix SMB2 client rename bug to a Windows server. o Andrew Bartlett <abartlet at samba.org> * BUG 14424: dsdb: Allow "password hash userPassword schemes =

Release Announcements --------------------- This is the latest stable release of the Samba 4.12 release series. Changes since 4.12.5 -------------------- o Jeremy Allison <jra at samba.org> * BUG 14403: s3: libsmb: Fix SMB2 client rename bug to a Windows server. o Andrew Bartlett <abartlet at samba.org> * BUG 14424: dsdb: Allow "password hash userPassword schemes =

Hi @all, in which version MAX_DEBUG_LEVEL in local.h and debug.h is available (not in 2.2.8a and not in 2.0.10a)? I want to get smaller binaries for the router system fli4l (router on a floppy) with reducing the amount of debugging informations. I have to use on of the above versions due last security fixes. I would prefere 2.0.10a, because it is smaller as 2.2.8a and has functionality enough for

Release Announcements ===================== This is the fourth release condidate of Samba 4.13. 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.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the fourth release condidate of Samba 4.13. 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.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the fifth release condidate of Samba 4.13. 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.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements ===================== This is the fifth release condidate of Samba 4.13. 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.13 will be the next version of the Samba suite. UPGRADING ========= NEW FEATURES/CHANGES

Release Announcements --------------------- This is the first stable release of the Samba 4.13 release series. Please read the release notes carefully before upgrading. ZeroLogon ========= Please avoid to set "server schannel = no" and "server schannel= auto" on all Samba domain controllers due to the wellknown ZeroLogon issue. For details please see

Release Announcements --------------------- This is the first stable release of the Samba 4.13 release series. Please read the release notes carefully before upgrading. ZeroLogon ========= Please avoid to set "server schannel = no" and "server schannel= auto" on all Samba domain controllers due to the wellknown ZeroLogon issue. For details please see

Release Announcements ===================== This is the sixth release condidate of Samba 4.13. 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.13 will be the next version of the Samba suite. SECURITY ======== o CVE-2020-1472: Unauthenticated

Release Announcements ===================== This is the sixth release condidate of Samba 4.13. 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.13 will be the next version of the Samba suite. SECURITY ======== o CVE-2020-1472: Unauthenticated

smb.conf # Global parameters [global] netbios name = DC0 dns forwarder = 192.168.2.4 realm = GRANMARMO.INTRANET server role = active directory domain controller workgroup = GRANMARMO ntlm auth = mschapv2-and-ntlmv2-only password hash userPassword schemes = CryptSHA256 CryptSHA512 rpc server dynamic port range = 50000-55000 loglevel = 30 auth:5 winbind:5 passdb:5 time server = yes

Hi Simon, Le 10/06/2016 11:12, blog at lesfourmisduweb.org a écrit : > > Yes it could be interesting. > I want to use it to send the password has an API for other software. I > currently use the "Store passwords using reversible encryption" to use > my API. But I do not like this operation. I then use >

interesting ! Let me take a closer look at that. I must send passwords in Office 365 and Google Apps. Currently, My script works but it requires that Samba is configured with the "Plain text Password" option. I want to change that. "Check password script" could solve my problem. "http://ltb-project.org/wiki/documentation/self-service-password" with " post

Release Announcements --------------------- This is an additional bugfix release of the Samba 4.10 release series to address the following issues: Changes since 4.10.15 --------------------- o Jeremy Allison <jra at samba.org> * s3: lib: Paranoia around use of snprintf copying into a fixed-size buffer from a getenv() pointer. o Amit Kumar <amitkuma at redhat.com> *

Release Announcements --------------------- This is an additional bugfix release of the Samba 4.10 release series to address the following issues: Changes since 4.10.15 --------------------- o Jeremy Allison <jra at samba.org> * s3: lib: Paranoia around use of snprintf copying into a fixed-size buffer from a getenv() pointer. o Amit Kumar <amitkuma at redhat.com> *

Unfortunately, there are other restrictions which disallow the use of macros in the active directory code, so it wouldn't be as simple as that. Thanks Denis for suggesting metze's branch. That might actually be the most appropriate way to solve this issue. Although there have been other ways of syncing passwords in the past, none of them are currently compatible with active directory.

Andreas, A few thoughts regarding your system 1) If it's a home system and you're specifically concerned about mitigating CVE 2017-7494, (a) verify that your share isn't mounted 'noexec' - if it's mounted this way then you're safe (b) if not (a), then add the [global] parameter "nt pipe support = no". This will break functionality that relies on support for

Release Announcements --------------------- This is the latest stable release of the Samba 4.12 release series. Changes since 4.12.2 -------------------- o Jeremy Allison <jra at samba.org> * BUG 14301: Fix smbd panic on force-close share during async io. * BUG 14343: s3: vfs_full_audit: Add missing fcntl entry in vfs_op_names[] array. * BUG 14361: vfs_io_uring: Fix data