Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-RT-Original-Encoding: iso-8859-1
Content-Length: 1488

Greetings<br>&nbsp;I am trying to study the MIT implementation of the protocol. I have noticed a problem when i try to<br>get a initial ticket with the pre auth list as <br>&nbsp;{ ETYPE_INFO2, ENC_TIMESTAMP}<br>( I have removed the prefix.)
<br>so when i pass this to krb5_get_init_... _password, I get a memory fault. I have traced it to preauth2.c<br>where in switch for ETYPE_INFO2 , I get a error return code from decode_krb5_etype_info2, and<br>when subsequent free is called (ignoring the return code) it crashes.
<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; if (ret) {<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ret = 0; /*Ignore error and etype_info element*/<br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; krb5_free_etype_info( context, etype_info);&nbsp;&nbsp; &lt;== crash <br>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; etype_info = NULL;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; continue;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br><br>My question is how is etype_info2 preauth suppposed to be used? The reason I want to do this,<br>so that I don't have to specify the encryption types for pre-auth (as the current implementation<br>seems to pick the first key which is aes...). 
<br>I don't know whether it is bug or not, but wanted to confirm this. This is based on 1.4.1 release <br>(although I have checked the 1.4.3 release and the affected files do not seem to have changed).<br><br>Thanks<br>Raj
<br>