Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jochen Hein <jochen@jochen.org>
Cc: Florian Weimer <fw@deneb.enyo.de>,  ding@gnus.org
Subject: Re: gssapi authentication for nnimap
Date: Mon, 08 Feb 2016 16:23:19 +1100	[thread overview]
Message-ID: <8737t3g4hk.fsf@gnus.org> (raw)
In-Reply-To: <83a8ncfnkc.fsf@echidna.jochen.org> (Jochen Hein's message of "Sun, 07 Feb 2016 18:16:35 +0100")

Jochen Hein <jochen@jochen.org> writes:

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

Nice.

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

We do still have the gssapi.el file, so we could presumably get this
stuff working again, if somebody with access to a server that uses
gssapi could hack away at it a bit...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2016-02-08  5:23 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 [this message]
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=8737t3g4hk.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=fw@deneb.enyo.de \
    --cc=jochen@jochen.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).