Displaying 3 results from an estimated 3 matches for "krb5cc_101125".
2015 Nov 02
4
Pam_mount not working with "sec=krb5"
...nged? Here it seems
that cache was ok in the past (see the end of the longest cited log part
in the middle; but there was a different problem, obviously, with
ownership):
http://www.spinics.net/lists/linux-cifs/msg05290.html
>/Jan 25 17:55:12 goto cifs.upcall: find_krb5_cc: considering
/tmp/krb5cc_101125/
>/Jan 25 17:55:12 goto cifs.upcall: find_krb5_cc: /tmp/krb5cc_101125 is
owned by 101125, not 0/
I mean, putting the key in the keytab looks like a security risk to me.
Would be nice if you could use kerberos on the fly.
Unfortunately, I don't find such a detailed log in /var/log/message...
2015 Nov 02
0
Pam_mount not working with "sec=krb5"
...he was ok in the past (see the end of the longest cited log
> part in the middle; but there was a different problem, obviously, with
> ownership):
> http://www.spinics.net/lists/linux-cifs/msg05290.html
>
>> /Jan 25 17:55:12 goto cifs.upcall: find_krb5_cc: considering
> /tmp/krb5cc_101125/
>> /Jan 25 17:55:12 goto cifs.upcall: find_krb5_cc: /tmp/krb5cc_101125 is
> owned by 101125, not 0/
>
> 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...
2015 Nov 02
3
Pam_mount not working with "sec=krb5"
Am 02.11.2015 um 13:12 schrieb buhorojo:
> On 02/11/15 12:54, Ole Traupe wrote:
>> Hi all, this is not really a Samba question, but related, and I hope
>> that some of you are using this and can tell me what I am doing wrong.
>>
>> On a member server, I can mount my shares by hand specifying "-o
>> username=xxx,domain=yyy,password=zzz". But as soon as I