Re: kinit: krb5_get_kdc_cred: KDC can't fulfill requested option

Victor Sudakov <[email protected]>
Newsgroups gmane.comp.encryption.kerberos.heimdal.general
Organization AO "Svyaztransneft", SibPTUS
Message-ID <[email protected]>
Harald Barth wrote:
> 
> > What should I specify in krb5.conf to always obtain renewable tickets? 
> 
> It might be missing from the man page, but I think it is
> 
> [libdefaults]
> 	renewable = true
> 

Indeed, after the first "kinit -R" the ticket looses it renewable
property. It is a desired/expected behaviour? Please see the output
below:


Script started on Sun Jun 26 10:22:42 2016
You have mail.
[sudakov@vas ~] klist
klist: No ticket file: /tmp/krb5cc_1001
[sudakov@vas ~] kinit
[email protected]'s Password:
[sudakov@vas ~] klist -v
Credentials cache: FILE:/tmp/krb5cc_1001
	Principal: [email protected]
    Cache version: 4

Server: krbtgt/[email protected]
Client: [email protected]
Ticket etype: aes256-cts-hmac-sha1-96, kvno 1
Ticket length: 433
Auth time:  Jun 26 10:22:49 2016
End time:   Jul  3 10:22:49 2016
Renew till: Jul  3 10:22:49 2016
Ticket flags: pre-authent, initial, renewable, forwardable
Addresses: IPv4:78.140.19.131, IPv4:192.168.4.1, IPv4:192.168.3.1, IPv6:2001:470:35:7af::2, IPv4:192.168.1.1

[sudakov@vas ~] kinit -R
[sudakov@vas ~] kinit -R
kinit: krb5_get_kdc_cred: KDC can't fulfill requested option
[sudakov@vas ~] klist -v
Credentials cache: FILE:/tmp/krb5cc_1001
	Principal: [email protected]
    Cache version: 4

Server: krbtgt/[email protected]
Client: [email protected]
Ticket etype: aes256-cts-hmac-sha1-96, kvno 1
Ticket length: 433
Auth time:  Jun 26 10:22:49 2016
Start time: Jun 26 10:22:54 2016
End time:   Jul  3 10:22:49 2016
Ticket flags: transited-policy-checked, pre-authent, forwardable
Addresses: IPv4:78.140.19.131, IPv4:192.168.4.1, IPv4:192.168.3.1, IPv6:2001:470:35:7af::2, IPv4:192.168.1.1

[sudakov@vas ~] exit

Script done on Sun Jun 26 10:23:00 2016

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN
sip:[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.