Thanks for working on Shishi support in InetUtils! Mats Erik Andersson <[email protected]> writes:
> * There was a call to shishi_done() executed from within > auth_finished() until yesterday. That lead to the premature > release of the Shishi handle, and sometimes segfaults. Do you know what kind of problems you'd get due to this? I have now set up a Shishi KDC on interop.josefsson.org so by using InetUtils and Shishi from Ubuntu 12.04 you can do this to acquire tickets: $ shishi [email protected] The password is 'pencil'. Then put default-realm interop.josefsson.org in your ~/.shishi/shishi.conf and then invoke telnet: inetutils-telnet -l user interop.josefsson.org You can verbose output using ~/.telnetrc: DEFAULT environ export XAUTHORITY set autodecrypt set autoencrypt set autologin # set authdebug set verbose_encrypt The output from telnet is: jas@latte:~$ inetutils-telnet -l user interop.josefsson.org Trying 178.79.173.181... Automatic decryption of input is enabled Automatic encryption of output is enabled Will send login name and/or authentication information. Encryption is verbose Connected to interop.josefsson.org. Escape character is '^]'. [ Kerberos V5 accepts you as ``interop.josefsson.org'' (server authenticated) ] [ Output is now encrypted with type DES_CFB64 ] [ Input is now decrypted with type DES_CFB64 ] However from there on it stalls. Sometimes it disconnected. The syslog on the server has plenty of these: <30>1 2012-08-08T12:04:56.490115+00:00 interop telnetd 6395 - - ttloop: retrying <30>1 2012-08-08T12:04:56.495418+00:00 telnetd 6395 - - last message repeated 199 times <46>1 2012-08-08T12:04:56.492126+00:00 interop rsyslogd-2177 - - imuxsock begins to drop messages from pid 6395 due to rate-limiting This behaviour looks consistent with the Shishi handle being unavailable after authentication has completed. /Simon
