Re: Kerberos functionality?

["William M. Perry" <wmperry@aventail.com>]

Ken Raeburn writes:
>"Michael Welsh Duggan" <md5i@schenley.com> writes:
>
>> Actually, high on my wish list is Kerberos for emacs, in the c-code,
>> with some functions to access it.  (Maybe integrated into
>> open-network-stream.)
>
>Go for it!  But put plenty of thought into how interrupts should be
>dealt with, blocking network i/o, that sort of thing.
>
>I don't think integrating into open-network-stream is the best way,
>though a lisp function that calls open-network-stream and then calls
>krb-sendauth on the subprocess object would be very useful.
>
>Of course, that still doesn't get us encryption....

  the way I implemented SSL was you used a normal open-network-stream to
connecto to a host.  Then there was a secondary call
'ssl-initialize-connection' that did all the SSL handshaking, etc, and
marked the process as 'sslified'.  Then the read/write routines for
processes were modified to check the sslified bit, and use SSLread/SSLwrite
if it was set.

  This turned out to be a great way to do it, because you could do all
sorts of things before the SSL connection was established - netscape-style
SSL proxying negotiation (which happens in the clear), still being able to
use telnet in a subprocess or the 'tcp' package from the old GNUS to get
outside your firewall, traversing a socks firewall, etc.

  It has been a _long_ time since I really looked at kerberos, but I'm sure
something similar could be done.  The real bitch was writing RSA
certificate manipulation functions that could be exported to the lisp
level.  Bleah.

-Bill P.