similar to: [Announce] Samba 4.21.3 Available for Download

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.1 -------------------- o? Ralph Boehme <slow at samba.org> ?? * BUG 15732: smbd fails to correctly check sharemode against OVERWRITE ???? dispositions. ?? * BUG 15754: Panic in close_directory. o? Pavel Filipensk? <pfilipensky at samba.org> ?? *

Release Announcements --------------------- This is the latest stable release of the Samba 4.21 release series. Changes since 4.21.1 -------------------- o? Ralph Boehme <slow at samba.org> ?? * BUG 15732: smbd fails to correctly check sharemode against OVERWRITE ???? dispositions. ?? * BUG 15754: Panic in close_directory. o? Pavel Filipensk? <pfilipensky at samba.org> ?? *

Dear all, Following [1] from a year ago, I'd like to know what is the state of the crossrename VFS module, and whether it's expected to be supported at least together with the recycle module? To be honest I'm quite sympathetic with the reasoning in [1] and I don't see a general use of crossrename. However, it remains relevant in the context of recycle, and currently I

Hi, I tried samba 4.12.0 on our file server which is a domain member and exporting some shares. We're getting some strange errors on some shares since the update. Right after starting or restarting smbd everything is fine. After short while (seconds or a few minutes) users are getting errors when trying to access the shares, e.q. "Invalid Handle Error", "An unexpected

On 10/03/2020 08:03, Andreas Hauffe via samba wrote: > We have a kerberized NFS4 running on that machine, too. I do hope that you are not resharing the NFS share(s) via Samba, that way lies madness ;-) Try this smb.conf: [global] ??????? workgroup = SUBDOM ??????? realm = SUBDOM.DOM.EXAMPLE.COM ??????? security = ADS ??????? bind interfaces only = Yes ??????? interfaces = lo enp1s0f0

Hi, My denyhosts stop working. How do i check why isnt it working anymore for me? Thanks Oct 2 22:59:17 beyond sshd[15690]: Failed password for root from 221.7.37.142 port 49836 ssh2 Oct 2 22:59:17 beyond sshd[15692]: Received disconnect from 221.7.37.142: 11: Bye Bye Oct 2 22:59:18 beyond sshd[15701]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser=

Thanks, I will give that a try. But I need the 'winbind separator = +'. We use some expensive commercial software (e.g. ANSYS, ABAQUS, ...), which uses shell scripts to start their software under linux. These scripts are not able to handle a backslash in the user name. The only solution was to switch to a "+" character. We reported these issues two years ago. Regards,

Am 11.07.24 um 12:47 schrieb Rowland Penny via samba: > Hi Stefan, I do not use use btrfs, so I cannot fully answer your > question, but a quick internet search using 'samba btrfs quota' turned > up this Samba bug: > > https://bugzilla.samba.org/show_bug.cgi?id=10541 > > Perhaps that will help. thank you. Hmm. I learned about vfs_btrfs now and set up a test share

Hi all, Is this something I should report in bugzilla? In my smb3.conf I have vfs object = recycle full_audit crossrename and when doing a classicupgrade, I'm getting a segmentation fault. It doesn't finish. (tried 4.1.2, 4.1.3, 4.1.4) When removing the line, the classicupgrade finishes successfully. It's easy to get around, but wouldn't it be nicer not to crash..?

Release Announcements --------------------- This is the first stable release of the Samba 4.19 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== Migrated smbget to use common command line parser ------------------------------------------------- The smbget utility implemented its own command line parsing logic. After discovering

Release Announcements --------------------- This is the first stable release of the Samba 4.19 release series. Please read the release notes carefully before upgrading. NEW FEATURES/CHANGES ==================== Migrated smbget to use common command line parser ------------------------------------------------- The smbget utility implemented its own command line parsing logic. After discovering

Release Announcements ===================== This is the fourth release candidate of Samba 4.21.? 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.21 will be the next version of the Samba suite. UPGRADING ========= Hardening of "valid

Release Announcements ===================== This is the fourth release candidate of Samba 4.21.? 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.21 will be the next version of the Samba suite. UPGRADING ========= Hardening of "valid

Hi, we have a stange problem here since samba 4.12. Users on specific clients are not allowed to access a share after reboot of the client and in very rare cases suddenly during use. When we restart the smb service after the access denied message on the client for a share, the user is allowed to access the share. So there seems no problem with permissions. Are there any known reasons for

Release Announcements --------------------- This is the latest stable release of the Samba 4.15 release series. Changes since 4.15.3 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 14928: Duplicate SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the

Release Announcements --------------------- This is the latest stable release of the Samba 4.15 release series. Changes since 4.15.3 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 14928: Duplicate SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the

Release Announcements --------------------- This is the latest stable release of the Samba 4.20 release series. Changes since 4.20.0 -------------------- o? Douglas Bagnall <douglas.bagnall at catalyst.net.nz> ?? * BUG 15630: dns update debug message is too noisy. o? Alexander Bokovoy <ab at samba.org> ?? * BUG 15635: Do not fail PAC validation for RFC8009 checksums types. o?

Release Announcements --------------------- This is the latest stable release of the Samba 4.20 release series. Changes since 4.20.0 -------------------- o? Douglas Bagnall <douglas.bagnall at catalyst.net.nz> ?? * BUG 15630: dns update debug message is too noisy. o? Alexander Bokovoy <ab at samba.org> ?? * BUG 15635: Do not fail PAC validation for RFC8009 checksums types. o?

Release Announcements --------------------- This is the latest stable release of the Samba 4.20 release series. Changes since 4.20.4 -------------------- o? Ralph Boehme <slow at samba.org> ?? * BUG 15695: "inherit permissions = yes" triggers assert() in vfs_default ???? when creating a stream. o? David Disseldorp <ddiss at samba.org> ?? * BUG 15699: Incorrect

Release Announcements --------------------- This is the latest stable release of the Samba 4.20 release series. Changes since 4.20.4 -------------------- o? Ralph Boehme <slow at samba.org> ?? * BUG 15695: "inherit permissions = yes" triggers assert() in vfs_default ???? when creating a stream. o? David Disseldorp <ddiss at samba.org> ?? * BUG 15699: Incorrect