From: Ken Raeburn <raeburn@cygnus.com>
Subject: Re: Kerberos functionality?
Date: 22 Jan 1997 19:30:35 -0500 [thread overview]
Message-ID: <tx1680ps05w.fsf@cygnus.com> (raw)
In-Reply-To: "Michael Welsh Duggan"'s message of 22 Jan 1997 16:42:13 -0500
"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....
next prev parent reply other threads:[~1997-01-23 0:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-22 17:09 John Twilley
1997-01-22 20:33 ` Rich Pieri
1997-01-22 21:42 ` Michael Welsh Duggan
1997-01-22 22:51 ` William M. Perry
1997-01-23 0:30 ` Ken Raeburn [this message]
1997-01-23 15:02 ` William M. Perry
1997-01-22 22:52 ` Ken Raeburn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tx1680ps05w.fsf@cygnus.com \
--to=raeburn@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).