search for: krb5cc_1494_sm11pg

...: scandir error on directory '/run/user/0': No such file or directory Feb 8 09:51:46 trog cifs.upcall: find_krb5_cc: considering /tmp/krb5cc_0 Feb 8 09:51:46 trog cifs.upcall: find_krb5_cc: FILE:/tmp/krb5cc_0 is valid ccache Feb 8 09:51:46 trog cifs.upcall: find_krb5_cc: considering /tmp/krb5cc_1494_sM11PG Feb 8 09:51:46 trog cifs.upcall: find_krb5_cc: /tmp/krb5cc_1494_sM11PG is owned by 1494, not 0 Feb 8 09:51:46 trog cifs.upcall: handle_krb5_mech: getting service ticket for smb.physics.wisc.edu Feb 8 09:51:46 trog cifs.upcall: handle_krb5_mech: obtained service ticket Feb 8 09:51:46 trog cifs.u...

...u diff them: uid=0 creduid=0 user=smbadmin at PHYSICS.WISC.EDU -pid=27600 -find_krb5_cc: scandir error on directory '/run/user/0': No such file or directory -find_krb5_cc: considering /tmp/krb5cc_0 -find_krb5_cc: FILE:/tmp/krb5cc_0 is valid ccache -find_krb5_cc: considering /tmp/krb5cc_1494_sM11PG -find_krb5_cc: /tmp/krb5cc_1494_sM11PG is owned by 1494, not 0 +pid=26578 +get_tgt_time: unable to get principal handle_krb5_mech: getting service ticket for smb.physics.wisc.edu handle_krb5_mech: obtained service ticket Exit status 0 That "get_tgt_time: unable to get principal"...

...t; the non-root user at mount time - what happens if the non-root user > hasn't kinit-ed yet? And yet that case worked in the past...) > I'm more interested in what the trailing info in your credcache name is. In your log output for the working case, there are: /tmp/krb5cc_0 /tmp/krb5cc_1494_sM11PG So first one doesn't have that _XXXXXX trailing bit. Maybe cifs.upcall is not guessing that piece of the filename correctly? In any case, this patch should tell us more about what it thinks the credcache location is when it's doing this. Do you have the ability to apply this and test with...

...worked in the past...) > > > > > > > > > > I'm more interested in what the trailing info in your credcache > > > name is. > > > In your log output for the working case, there are: > > > > > > /tmp/krb5cc_0 > > > /tmp/krb5cc_1494_sM11PG > > > > > > So first one doesn't have that _XXXXXX trailing bit. Maybe > > > cifs.upcall > > > is not guessing that piece of the filename correctly? > > > > > > > (cc'ing Nalin, Simo and the linux-cifs ml) > > > > Yeah...

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'm more interested in what the trailing info in your credcache > > > > > name is. > > > > > In your log output for the working case, there are: > > > > > > > > > > /tmp/krb5cc_0 > > > > > /tmp/krb5cc_1494_sM11PG > > > > > > > > > > So first one doesn't have that _XXXXXX trailing bit. Maybe > > > > > cifs.upcall > > > > > is not guessing that piece of the filename correctly? > > > > > > > > > > > > > (c...