similar to: [Announce] Samba 4.1.0rc3 Available for Download

================================================================== "Insanity: doing the same thing over and over again and expecting different results." Albert Einstein ================================================================== Release Announcements --------------------- This is is the first stable release of Samba 4.1. Samba 4.1 will be the next version

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

================================================================== "Insanity: doing the same thing over and over again and expecting different results." Albert Einstein ================================================================== Release Announcements --------------------- This is is the first stable release of Samba 4.1. Samba 4.1 will be the next version

================================================================== "Insanity: doing the same thing over and over again and expecting different results." Albert Einstein ================================================================== Release Announcements --------------------- This is is the first stable release of Samba 4.1. Samba 4.1 will be the next version

Release Announcements ===================== This is the second 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 second 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

In current kernels we have the new IOCTL / QueryInfo passthrough where you can use a simple ioctl() on an object in a SMB2/3 share and pull the full security descriptor. It would be fairly trivial to expand this to allow setting the security descriptor too using SetInfo. We can add that when there is a need. Now, since this is available through a simple ioctl() interface, you can access this

ACL management can be done for SMB2/SMB3 ACLs with two common tools depending on your preference. smbcacls (somewhat similar to using cacls.exe or icacls.exe in Windows but specifying the UNC name rather than a local path name). smbcacls sets up and tears down a network connection each time it is run and uses Samba user space code. or setcifsacl/getcifsacl (which calls cifs.ko to access the

Thanks for the first reply, Jeremy. What about the (future) implementation of RichACL? Will there be any native Linux Client support along with the SMB2/SMB3 protocol? I know, there is a native implemenation for RichACLs in ext4 FS. Unfortunately, smbcals is not a native Linux ACL Tool and has a very unhandy syntax. I just tested some days ago. ;-) I am looking for a solution that allows the

On Sun, Sep 16, 2018 at 09:53:59AM +0200, MI via samba wrote: > We have a 10G network with a mix of Windows 10 and MacOS 10.12 machines, and > a CentOS 7 machine. > > Copying large files "fast" from the CentOS machine to Windows, using SMB2 or > SMB3 fails almost every time, at the end of the copy. > - With SMB1, it seems to work, but is much slower. > - Copying to

>> - smbclient [no -m option] is OK and slow (uses default SMB1/NT1?) >> - mount.cifs -o vers=1.0 is OK and slow >> - smbclient -m SMB2 (or -m SMB3) fails > The above is the interesting case, as this is much > easier to debug (in user space) than the kernel > client. > > Can you give more details on *exactly* HOW smbclient -mSMB3 > fails ? This is really

On Tue, Feb 26, 2019 at 03:05:12PM +0000, Kraus, Sebastian via samba wrote: > Dear all, > what is about the support for POSIX ACL in Samba protocol implementation of SMB2 and SMB3? > From what I extracted from SNIA and SambaXP developer conference talks and as well as the official Samba Wiki, > support for POSIX ACL in SMB2 and SMB3 has been completely abandonned. Am I right? Yes.

Hello I try today to install samba 4.13.1 ? ./configure run without error Make run without error Make Check Failed Debian 10.6 Also all required Packages are installed -- # cat summary = Failed tests = == samba4.blackbox.demote-saveddb == command: PYTHON=python3 /usr/src/samba-4.13.1/testprogs/blackbox/demote-saveddb.sh $PREFIX_ABS/demote

On Thu, 27 Oct 2016 16:57:13 -0700, Jeremy Allison <jra at samba.org> wrote : > On Fri, Oct 28, 2016 at 01:42:35AM +0200, Saint Germain via samba > wrote: > > On Thu, 27 Oct 2016 16:27:05 -0700, Jeremy Allison <jra at samba.org> > > > if you see any of these then it happened. > > > > Ok I understand how to check that it happened, but how can I make

Dear all, what is about the support for POSIX ACL in Samba protocol implementation of SMB2 and SMB3? >From what I extracted from SNIA and SambaXP developer conference talks and as well as the official Samba Wiki, support for POSIX ACL in SMB2 and SMB3 has been completely abandonned. Am I right? If so, is there any other possibility to allow Linux Clients to natively access access control lists

We have a 10G network with a mix of Windows 10 and MacOS 10.12 machines, and a CentOS 7 machine. Copying large files "fast" from the CentOS machine to Windows, using SMB2 or SMB3 fails almost every time, at the end of the copy. - With SMB1, it seems to work, but is much slower. - Copying to a smb share on a Mac seems to work, but is also much slower. - Using a normal Gigabit network

Release Announcements ===================== This is the first 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 first 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

On Thu, Jun 08, 2017 at 02:40:49PM -0700, Jeremy Allison wrote: > On Thu, Jun 08, 2017 at 06:43:34PM +0200, Ralph Böhme via samba wrote: > > Hi Andy, > > > > On Thu, Jun 08, 2017 at 09:23:50AM -0700, Andy Qian via samba wrote: > > > The smbcacls cmd worked before till recently. Due to the recent Windows > > > patch which disables SMB v1, we have to add the