search for: krb5cc_12345_afcdeb

...This was formerly acquired interactively via username/password, and that way you have something like a single sign-on. This is what works so far: 1. log in as the domain user 'userxyz' (id=12345) via ssh to a Linux member server -> the kerberos cache file is created in /tmp ("krb5cc_12345_afcdeb") 2. while the user is logged in (and the cache exists), use this command to mount his home share (as root): # mount.cifs //server/home/userxyz /home/userxyz -o sec=krb5,cruid=12345,uid=12345,gid=someGroupID So, users' krb5 cache files are actually used by the cifs mount upcall. I made...

...ssword, and that way you have something like a single >> sign-on. >> >> This is what works so far: >> >> 1. log in as the domain user 'userxyz' (id=12345) via ssh to a Linux >> member server -> the kerberos cache file is created in /tmp >> ("krb5cc_12345_afcdeb") >> 2. while the user is logged in (and the cache exists), use this command to >> mount his home share (as root): >> # mount.cifs //server/home/userxyz /home/userxyz -o >> sec=krb5,cruid=12345,uid=12345,gid=someGroupID >> >> So, users' krb5 cache files...

...t;>>> sign-on. >>>> >>>> This is what works so far: >>>> >>>> 1. log in as the domain user 'userxyz' (id=12345) via ssh to a Linux >>>> member server -> the kerberos cache file is created in /tmp >>>> ("krb5cc_12345_afcdeb") >>>> 2. while the user is logged in (and the cache exists), use this command >>>> to >>>> mount his home share (as root): >>>> # mount.cifs //server/home/userxyz /home/userxyz -o >>>> sec=krb5,cruid=12345,uid=12345,gid=someGroupID &...

...ctively > via username/password, and that way you have something like a single > sign-on. > > This is what works so far: > > 1. log in as the domain user 'userxyz' (id=12345) via ssh to a Linux > member server -> the kerberos cache file is created in /tmp > ("krb5cc_12345_afcdeb") > 2. while the user is logged in (and the cache exists), use this command to > mount his home share (as root): > # mount.cifs //server/home/userxyz /home/userxyz -o > sec=krb5,cruid=12345,uid=12345,gid=someGroupID > > So, users' krb5 cache files are actually used by the...

...e something like a single >>> sign-on. >>> >>> This is what works so far: >>> >>> 1. log in as the domain user 'userxyz' (id=12345) via ssh to a Linux >>> member server -> the kerberos cache file is created in /tmp >>> ("krb5cc_12345_afcdeb") >>> 2. while the user is logged in (and the cache exists), use this command >>> to >>> mount his home share (as root): >>> # mount.cifs //server/home/userxyz /home/userxyz -o >>> sec=krb5,cruid=12345,uid=12345,gid=someGroupID >>> >>...

...t;>>> sign-on. >>>> >>>> This is what works so far: >>>> >>>> 1. log in as the domain user 'userxyz' (id=12345) via ssh to a Linux >>>> member server -> the kerberos cache file is created in /tmp >>>> ("krb5cc_12345_afcdeb") >>>> 2. while the user is logged in (and the cache exists), use this command >>>> to >>>> mount his home share (as root): >>>> # mount.cifs //server/home/userxyz /home/userxyz -o >>>> sec=krb5,cruid=12345,uid=12345,gid=someGroupID &...

>> I mean, putting the key in the keytab looks like a security risk to me. > In what way does it appear any more of a risk than having the keys > which you have there already? Even if someone steals the keytab, > they're gonna be hard pressed to crack the key in the few hours before > the tgt expires. Do you have very sensitive data maybe? Ok. And maybe I misunderstood

...gt;>>> > >>>> This is what works so far: > >>>> > >>>> 1. log in as the domain user 'userxyz' (id=12345) via ssh to a Linux > >>>> member server -> the kerberos cache file is created in /tmp > >>>> ("krb5cc_12345_afcdeb") > >>>> 2. while the user is logged in (and the cache exists), use this > command > >>>> to > >>>> mount his home share (as root): > >>>> # mount.cifs //server/home/userxyz /home/userxyz -o > >>>> sec=krb5,cruid=123...

...>>>>> >>>>> This is what works so far: >>>>> >>>>> 1. log in as the domain user 'userxyz' (id=12345) via ssh to a Linux >>>>> member server -> the kerberos cache file is created in /tmp >>>>> ("krb5cc_12345_afcdeb") >>>>> 2. while the user is logged in (and the cache exists), use this command >>>>> to >>>>> mount his home share (as root): >>>>> # mount.cifs //server/home/userxyz /home/userxyz -o >>>>> sec=krb5,cruid=12345,uid=123...