From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jochen Hein <jochen@jochen.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
ding@gnus.org, Florian Weimer <fw@deneb.enyo.de>
Subject: Re: gssapi authentication for nnimap
Date: Wed, 10 Feb 2016 15:30:39 +1100 [thread overview]
Message-ID: <87twlhi3v4.fsf@gnus.org> (raw)
In-Reply-To: <83si1142u6.fsf@echidna.jochen.org> (Jochen Hein's message of "Wed, 10 Feb 2016 05:16:33 +0100")
Jochen Hein <jochen@jochen.org> writes:
> That seems to be the way forward, yes. I guess that the wrapper willl
> look a lot like open-protocol-stream... I'll have a try in the next few
> days.
An idea just occurred to me... This is the definition of
open-network-stream is this:
(open-network-stream NAME BUFFER HOST SERVICE &rest PARAMETERS)
[...]
:type specifies the connection type, one of the following:
nil or ‘network’
-- Begin with an ordinary network connection, and if
the parameters :success and :capability-command
are also supplied, try to upgrade to an encrypted
connection via STARTTLS. Even if that
fails (e.g. if HOST does not support TLS), retain
an unencrypted connection.
‘plain’ -- An ordinary, unencrypted network connection.
‘starttls’ -- Begin with an ordinary connection, and try
upgrading via STARTTLS. If that fails for any
reason, drop the connection; in that case the
returned object is a killed process.
‘tls’ -- A TLS connection.
‘ssl’ -- Equivalent to ‘tls’.
‘shell’ -- A shell connection.
We could extend this to `function', and that function would then deliver
the socket top `open-network-stream'. It'd be exactly like `shell', but
instead of calling the shell, we'd call the function.
The function in this case would be a slight variation over
open-gssapi-stream.
Or rather, it would kinda look like this:
(open-network-stream NAME BUFFER HOST SERVICE
... :type 'function
:connection-function (lambda (name buffer host service parameters)
(open-gssapi-stream name buffer server port nnimap-user)))
Wouldn't that do the trick with the minimal amount of hacking? If so, I
can add the :type 'function to open-network-stream on the Emacs trunk...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-10 4:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 14:35 Florian Weimer
2016-02-06 6:40 ` Lars Ingebrigtsen
2016-02-07 17:16 ` Jochen Hein
2016-02-08 5:23 ` Lars Ingebrigtsen
2016-02-08 9:51 ` Jochen Hein
2016-02-08 20:59 ` Jochen Hein
2016-02-08 21:51 ` Andreas Schwab
2016-02-08 23:21 ` Jochen Hein
2016-02-08 23:47 ` Andreas Schwab
2016-02-09 6:22 ` Jochen Hein
2016-02-09 20:05 ` Jochen Hein
2016-02-09 23:31 ` Lars Ingebrigtsen
2016-02-10 4:16 ` Jochen Hein
2016-02-10 4:23 ` Lars Ingebrigtsen
2016-02-10 4:30 ` Lars Ingebrigtsen [this message]
2016-02-10 4:42 ` Jochen Hein
2016-02-10 4:50 ` Lars Ingebrigtsen
2016-02-10 21:37 ` Jochen Hein
2016-02-11 19:51 ` [PATCH] GSSAPI " Jochen Hein
2016-02-13 6:50 ` Lars Ingebrigtsen
2016-02-13 10:30 ` Jochen Hein
2016-02-14 2:25 ` Lars Ingebrigtsen
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=87twlhi3v4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=fw@deneb.enyo.de \
--cc=jochen@jochen.org \
--cc=schwab@linux-m68k.org \
/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).