From: Jochen Hein <jochen@jochen.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Florian Weimer <fw@deneb.enyo.de>, ding@gnus.org
Subject: Re: gssapi authentication for nnimap
Date: Sun, 07 Feb 2016 18:16:35 +0100 [thread overview]
Message-ID: <83a8ncfnkc.fsf@echidna.jochen.org> (raw)
In-Reply-To: <87d1sanxyx.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 06 Feb 2016 17:40:06 +1100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Florian Weimer <fw@deneb.enyo.de> writes:
>
>> In the past, it was possible to authenticate to an IMAP server using
>> GSSAPI (over a TLS connection). This enabled me to use an active
>> Kerberos ticket to authenticate to a Zimbra email server. The old way
>> of configuring this no longer works. Is there a replacement?
>
> I think somebody was working on this? But I don't recall what the
> outcome was. Anybody remember?
I've recently tried it. The following worked for me:
(setq gnus-secondary-select-methods
'((nnml "private")
(nnimap "jochen@jochen.org"
(nnimap-expunge t)
(nnimap-stream shell)
(nnimap-shell-program "echo -e '* PREAUTH\r\n'; imtest %s %p -m GSSAPI")
(nnimap-address "imap.jochen.org"))
...
We should remove references in the gnus manual to gssapi or reference
nnimap-shell-program. I'm not sure that the following gssapi options
would be still useful:
`:stream'
What stream to use for connecting to the server, this is one
of the symbols in `imap-stream-alist'. Right now, this means
`gssapi', `kerberos4', `starttls', `tls', `ssl', `shell' or
the default `network'.
`:authentication'
Which authenticator to use for authenticating to the server,
this is one of the symbols in `imap-authenticator-alist'.
Right now, this means `gssapi', `kerberos4', `digest-md5',
`cram-md5', `anonymous' or the default `login'.
Jochen
--
The only problem with troubleshooting is that the trouble shoots back.
next prev parent reply other threads:[~2016-02-07 17:16 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 [this message]
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
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=83a8ncfnkc.fsf@echidna.jochen.org \
--to=jochen@jochen.org \
--cc=ding@gnus.org \
--cc=fw@deneb.enyo.de \
--cc=larsi@gnus.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).