Re: Keytab MEMORY in error message

2007-02-08 Thread Love Hörnquist Åstrand
Perhaps lib/krb5/keytab.c:krb5_kt_get_entry around line 372 should have: 371 krb5_kt_get_name (context, id, kt_name, sizeof(kt_name)); 372 krb5_enctype_to_string(context, enctype, enctype_str); if (kt_name[0] == '\0') strcpy(kt_name, MEMORY); 373 374

Re: Keytab MEMORY in error message

2007-02-08 Thread Love Hörnquist Åstrand
8 feb 2007 kl. 15.49 skrev Michael B Allen: Also, I would like to mention a very very minor issue related to the message above. If lib/krb5/get_in_tkt.c:init_as_req is called with krb5_kt_get_entry as key_proc and it does not find the desired key, the enctype listed in the error message will

Re: Keytab MEMORY in error message

2007-02-08 Thread Michael B Allen
On Fri, 9 Feb 2007 12:28:40 +1100 Love Hörnquist Åstrand [EMAIL PROTECTED] wrote: Perhaps lib/krb5/keytab.c:krb5_kt_get_entry around line 372 should have: 371 krb5_kt_get_name (context, id, kt_name, sizeof(kt_name)); 372 krb5_enctype_to_string(context, enctype,

Re: Keytab MEMORY in error message

2007-02-08 Thread Michael B Allen
On Fri, 9 Feb 2007 12:41:40 +1100 Love Hörnquist Åstrand [EMAIL PROTECTED] wrote: 8 feb 2007 kl. 15.49 skrev Michael B Allen: Also, I would like to mention a very very minor issue related to the message above. If lib/krb5/get_in_tkt.c:init_as_req is called with krb5_kt_get_entry as