Gnus development mailing list
 help / color / mirror / Atom feed
From: Jochen Hein <jochen@jochen.org>
To: Lars Ingebrigtsen <larsi@gnus.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 05:42:47 +0100	[thread overview]
Message-ID: <834mdh89bs.fsf@echidna.jochen.org> (raw)
In-Reply-To: <87twlhi3v4.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 10 Feb 2016 15:30:39 +1100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> 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...
...
> 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...

I'm not sure.  Right now open-gssapi-stream kills the greeting with
erase-buffer.  We need to scrapt greeting first, if needed.  Or
something like that.  I think I'll have to explore some different paths
to see what might be the best way forward.

Jochen

-- 
The only problem with troubleshooting is that the trouble shoots back.



  reply	other threads:[~2016-02-10  4:42 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
2016-02-10  4:42                         ` Jochen Hein [this message]
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=834mdh89bs.fsf@echidna.jochen.org \
    --to=jochen@jochen.org \
    --cc=ding@gnus.org \
    --cc=fw@deneb.enyo.de \
    --cc=larsi@gnus.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).