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 10:31:39 +1100 [thread overview]
Message-ID: <87egcl795w.fsf@gnus.org> (raw)
In-Reply-To: <83wpqd4pk6.fsf@echidna.jochen.org> (Jochen Hein's message of "Tue, 09 Feb 2016 21:05:45 +0100")
Jochen Hein <jochen@jochen.org> writes:
> Right now I have the following diff to nnimap.el. The second hunk
> hardcodes the imap port number - I didn't get that to work otherwise.
> In the third hunk I call open-gssapi-stream directly -
> open-protocol-stream doesn't handle the nnimap-user. Should that be
> added to open-protocol-stream?
No, open-protocol-stream shouldn't know anything about nnimap.
> + (let* ((stream-list
> + (if (eq nnimap-stream 'gssapi)
> + (list (open-gssapi-stream
> + "*nnimap*" (current-buffer) nnimap-address
> + (nnimap-map-port (car ports)) nnimap-user))
That looks OK...
> My current guess is that my gssapi-session is already authenticated,
> but nnimap-open-connection-1 after "ZZZ" is getting confused somehow.
>
> Some more debugging shows, that the next statement fails:
>
> (if (not (gnus-string-match-p "[*.] \\(OK\\|PREAUTH\\)" greeting))
> (nnheader-report 'nnimap "%s" greeting)
>
> That is somewhat expected, since my call to open-gssapi-stream doesn't
> set greeting (and I'm almost sure that later capability will also fail).
open-protocol-stream returns the greetings and the capabilities, but
open-gssapi-stream doesn't do that. So perhaps there should be a
wrapper around the latter function that will save the greeting and issue
the capability command?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-09 23:31 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 [this message]
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
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=87egcl795w.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).