similar to: cifs-utils release 6.10 ready for download

This is a big release that contains many functional changes that are aligned with the recent work done in the Linux SMB3 kernel client. These changes mostly aim to improve user experience by unlocking new features available in modern SMB3 servers: - smbinfo utility is added to query various kinds of information from the server (objectId, snapshots, different FileInfo* classes and other

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Things have been relatively quiet lately. Time for a release! Highlights: * A lot of manpage updates, additions and corrections * cifs.idmap can now map uid/gid to SID in addition to the other way around * getcifsacl/setcifsacl are now installed by default in /usr/bin instead of /usr/sbin. The manpages are now in section 1. * cifs.upcall has a

Hi When I mount CIFS share (mount -t cids) with vers=1.0 I can perform getcifsacl sucessfully. But when I mount with vers=2.0, or 2.1, or 3.0, ACL reading fails. getxattr error: 95 REVISION:0x0 CONTROL:0x0 Why getcifsacl depends on SMB protocol version? Can I read ACL via newer SMB protocol? A asked on Serverfault but without reply:

Dear Jeremy, thanks for your instant reply. :-) Along with Linux native getfacl/fetfacl, I also tested getcifsacl/setcifsacl (for sure thoroughly ;-)). Unfortunately, these CIFS client tools seem to have been designed as part of the "old" CIFS Unix Extensions, working only for SMB/CIFS mounts, and are not supposed to work with SMB2/SMB3 mounts, as I guess. During my tests, the

Hai, Ik have tried the option: follow symlinks = yes, but this also doesnt work. My workstation is XP SP3. Im also having some CIFS VFS messages on my console, kern.log.0:Mar 30 20:47:52 ms249-lin-001 kernel: [12804.264823] CIFS VFS: strtoUCS: char2uni of -121 returned -22 kern.log.0:Mar 30 20:47:52 ms249-lin-001 kernel: [12804.323034] CIFS VFS: strtoUCS: char2uni of -127 returned -22

On Wed, 23 Jan 2019 09:47:11 +0100 Miloslav Hůla via samba <samba at lists.samba.org> wrote: > Dne 2019-01-15 v 13:22 Miloslav Hůla via samba napsal(a): > > When I mount CIFS share (mount -t cids) with vers=1.0 I can perform > > getcifsacl sucessfully. But when I mount with vers=2.0, or 2.1, or > > 3.0, ACL reading fails. > > > > getxattr error: 95 >

Help .. I've struggled with this for a few weeks and can't get anywhere. I'd like for someone to point me in the right direction, if possible. I have laid out below my complete samba setting in the hope that 1) Someone can find a solution to my current problem 2) It might help someone else, as I overcame a few problems with these settings myself, under samba 2.2.8a.. please note

I may have a clue. I have two servers running Samba 3.2.3, one as a Domain Controller one as a Member Server. Both are running Ubuntu 8.10. smbd, nmbd and winbindd using the tdb back end are running on both. On the Member Server when I access the [Projects] share everything works as expected. When I access the [Windows] share I get prompted for a user name and password but no combination

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Time for a new cifs-utils release! The big bullet point in this release is a new pam_cifscreds module that has been added by Orion Poplawski. This release also cleans some unused cruft out of some of the binaries so they're quite a bit smaller now and fixes a few bugs that Coverity turned up. Go forth and download! webpage:

Sometimes a group sid does not get resolved to its name. Is this a settings problem? Looks like winbind deamon went dormant for a while and then woke up? I am using interface wbcLookupSid provided by the library libwbclient.so for resolving sids to names. These are the winbind related parameters in /etc/samba/smb.conf [global] # separate domain and username with '\', like

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Time for another cifs-utils release! Most of the patches in this release are for cifs.idmap, getcifsacl and setcifsacl. There were many bugs in those tools, so anyone that's deploying or using them is highly encouraged to upgrade. Highlights: * NFS-style device names are being deprecated in 6.0. Anyone using that sort of device name should

Hi, I have a regression test suite that creates this simple share: [tmp] comment = Temp Directory guest ok = Yes path = /tmp read only = No This is mounted via SMB1: mount //localhost/tmp -o guest,vers=1.0 /mnt The client (ubuntu 18.10 dev) is using cifs-utils 2:6.8-2 from debian (it's a sync). Client and server are the same machine (localhost). When the server is

We've had a number of changes since the last release, and we have some other upcoming kernel changes that might require corresponding cifs-utils changes. So it's probably as good a time as any for a new release. Highlights: + fix for a minor security issue that can corrupt the mtab + new getcifsacl/setcifsacl tools that allow you to fetch and set raw Windows ACLs via an xattr. + a

I need to access several Windows domain shares from my linux box. I can access both shares from a Win box where I use my domain login. I placed my domain credentials in /home/przemek/.smb_credentials and I can successfully mount one of the shares: mount.cifs '//elwood.nist.gov/61_NCNR/610' /mnt/ --verbose -o uid=przemek,credentials=/home/przemek/.smb_credentials parsing options:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 With the merge of the new plugin interface, it's probably a good time for a new cifs-utils release. Distro packagers should take special note of the changes with the new plugin interface since it has implications for how the tools are packaged. In particular, it's necessary to set a symlink to the plugin in the correct location

Hello all at the samba list. The other day there was a migration of server; the old one had Samba 2.2 (.6) working normally. Every user logged in the domain without problems, their SIDs and the domain SID were right, everything was ideal. But a server update was needed, and a new server was installed, also with Samba 2.2 (.12). The difference in version is not important this time as other

Could you see if anything useful in the logs indicating why the ACL was not returned? Instructions are at: https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting#Enabling_Debugging (it is easier for newer kernels due to dynamic tracing e.g. "trace-cmd record -e cifs" but even with these older kernels it should be enough information in the dmesg logs - if not a wireshark trace

I'm trying to understand the python binding api in the samba-3.0alpha24 snapshot. In trying to get the security descriptor of a file, I have the following bit of code: from samba import smb creds = {...} # domain,username,password cnn = smb.connect("svr1") cnn.session_request("svr1") cnn.negprot() cnn.session_setup(creds) cnn.tconx("c$") fnum =

Should I be able to share .Personal? I have it set up like all the other shares with the same permissions as some other shares. The other shares are mountable on a remote server but this one gives me [182021.389951] CIFS: Attempting to mount \\10.0.0.10\Personal [182021.390934] CIFS: VFS: cifs_mount failed w/return code = -13 smb.conf: [Personal] comment = Personal create mask = 02774

Hi Jeremy, Hi Steve, Hi Ronnie, thanks for your replies and the profound discussion. I think, it's best to demonstrate my problem case along an real world example: The following log of a console sesssion shows how I am doing the mounts on behalf Linux Kernel CIFS-FS Module on the client side against a Samba 4.5 file server (both running on Debian Stretch 9.8) via SMB/CIFS resp. SMB2 protocol: