similar to: how to mount shares as a user without mount.cifs setuid

Apologies for v3 series, I had some extra patches in there. This is the one that should have been sent. Relabeled as v4 for clarity. Third respin of this series. Reordered for better safety for bisecting. The environment scraping is now on by default, but can be disabled with "-E" in environments where it's not needed. Also, I've added a patch to make cifs.upcall drop

Third respin of this series. Reordered for better safety for bisecting. The environment scraping is now on by default, but can be disabled with "-E" in environments where it's not needed. Also, I've added a patch to make cifs.upcall drop capabilities before doing most of its work. This may help reduce the attack surface of the program. Jeff Layton (4): cifs.upcall: convert

On Fri, 2017-02-10 at 11:15 -0600, Chad William Seys wrote: > Hi Jeff, > > > So we have a default credcache for the user for whom we are operating > > as, but we can't get the default principal name from it. My guess is > > that it's not finding the > > This mount is run by root UID=0 and seems to be find that credential > cache without problem (earlier

Small respin of the patches that I posted a few days ago. The main difference is the reordering of the series to make it do the group and grouplist manipulation first, and then the patch that makes it grab the KRB5CCNAME from the initiating process. I think the code is sound, my main question is whether we really need the command-line switch for this. Should this just be the default mode of

Chad reported that he was seeing a regression in cifs-utils-6.6. Prior to that, cifs.upcall was able to find credcaches in non-default FILE: locations, but with the rework of that code, that ability was lost. Unfortunately, the krb5 library design doesn't really take into account the fact that we might need to find a credcache in a process that isn't descended from the session. When the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Time for another cifs-utils release! Nothing terribly earth shattering here. Some distros (like Fedora) are moving krb5 credcaches out of /tmp by default. Users of these distros will definitely want to upgrade. Highlights: * Fixes for mounting with '/' in usernames with sec=krb5 * Support for DIR: type krb5 ccaches * support for

Files on my Vista mount always have the S mode (setgid bit?) set according to ls -l. This is a security hole and causes other problems. I can't clear the bit with chmod; in fact the results of doing chmod don't make any sense to me (I'll be glad to provide examples). Typical files show as -rwxrwSrwx, though not all. The smb.conf file has create mask 0666 and directory mask 0777 various

Hi Aurélien, Thanks for the idea! For Debian packages: 6.4-1 works 6.5-1 works 6.5-2 works 6.6-1 fails 6.6-5 fails So looks like something changed from 6.5 to 6.6... When I have time I'll figure out how to compile the upcall binary.

This release is primarily a number of small bugfixes and cleanups. I wanted to do a release with those prior to the coming overhaul of mount.cifs to allow it to more safely be installed setuid root. There a couple of other noticeable changes too: - the version reported by all programs in the tarball now matches the VERSION define set by autoconf. That is, if someone runs "mount.cifs

Hi , I have French CIFS server. If I try to map a share from any windows machine with non-ascii (UTF-8, french characters are part of password) password, it is successful. But If I try from linux machine, it fails. mount -t cifs //MACHINE/DatasetFIGS_?????????????  /tmp/rahul -o user=??,password=??,domain=eKKDr mount error 13 = Permission denied Refer to the mount.cifs(8) manual

Hello, I need to mount a CIFS share (in the end via fstab, for now manually from terminal) which has both a space and a german umlaut in its name. I cannot get mount.cifs to mount it, it always complains it cannot find it. I managed to get around the space problem in fstab with the \040 trick, but I cannot find a way to correctly encode the umlaut. When looking at the output of "mount.cifs

Hi. I just got a new Windows 7 Home Edition computer and am unable to mount its shares on my Linux system. I'm running Fedora 11, samba 3.4.7 I have no trouble mounting shares from XP systems on the network using the mount command below. I can access the Windows 7 share with no problems using smbclient on Linux. The Windows 7 share is accessible from the XP systems. Here is the mount

Hi Samba team, I feel user will feel more confortable when they can mount folder (via mount.cifs or mount.smbfs) under particular shared folder. Example: I have a share folder call department, all department's folder arrange inside so I have a share folder call \\server\department if I have a linux client under purchasing, I 2 command to get the correct place, and I feel it is giving more

A sysadmin moved a share from one Windows server to another. I am now getting error 13 when trying to mount the share from the new server. The following worked before the server was replaced: mount.cifs //ipaddress1/share1$ /mnt/share1 -o credientials/home/whatever/.smbcredentials,rw mount.cifs //ipaddress2/share2$ /mnt/share2 -o credientials/home/whatever/.smbcredentials,ro Change: server

On Thu, 2017-02-09 at 14:45 -0600, Chad William Seys wrote: > Hi Jeff, > Could you look at the following mailing list posting? > > https://lists.samba.org/archive/samba/2017-February/206468.html > > It looks like cifs.upcall has changed its behavior. As described in > that post, I can mount with root / kerberos, but then cannot access with > another user who has

I have a debian machine called "debian" and a windows XP machine called "server". I have a permanent mounted read-only share called \\server\doc. My /etc/fstab looks like this: //server/doc /opt/chroot/mnt/server cifs credentials=/root/.smbmount,username=medical,uid=medical,file_mode=0755,dir_mode=0755,noserverino 0 0 This works well most of the time but at times I get a

Hello, Trying to compile Samba 3.2.15 on a RHEL AS 4u2 (i686) and I'm getting the following result from 'sh makerpms.sh': > Provides: samba-doc = 3.2.15-1 > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(VersionedDependencies) <= 3.0.3-1 > > > RPM build errors: > File not found:

I am confused (nothing new there ...). I have 2 Ubuntu 9.10 Samba servers. I am trying to mount a share from the other (i.e., "workhorse" is trying to mount a share on "dual-booter"). If I specify a smbmount command with a -k option, I can mount the share: turgon at workhorse:~$ klist Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: turgon at DACRIB.LOCAL Valid starting

Dear all, I'm fairly new to Samba and CIFS and, for that matter, Linux in general. I'm having a problem with "mount.cifs" as provided with Debian 5. I'm afraid I cannot say what version of mount.cifs I have since doing "mount.cifs -V" does not (contrary to the message it shows when I do this) actually show the version, but rather how to use the program. The

Release Announcements ===================== This is a security release in order to address CVE-2009-2813, CVE-2009-2948 and CVE-2009-2906. o CVE-2009-2813: In all versions of Samba later than 3.0.11, connecting to the home share of a user will use the root of the filesystem as the home directory if this user is misconfigured to have an empty home directory in /etc/passwd.