Gnus development mailing list
 help / color / mirror / Atom feed
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: [PATCH] GSSAPI authentication for nnimap
Date: Sat, 13 Feb 2016 17:50:51 +1100	[thread overview]
Message-ID: <87oablkss4.fsf@gnus.org> (raw)
In-Reply-To: <834mdfdo0c.fsf_-_@echidna.jochen.org> (Jochen Hein's message of "Thu, 11 Feb 2016 20:51:15 +0100")

Jochen Hein <jochen@jochen.org> writes:

> The following patches add GSSAPI support to nnimap.  I'll comment what I
> did and why above each patch.  I'm currently cloning the emacs
> repository and I hope to forward port the patches and add/adapt the
> documentation accordingly.

Great!

> This post is to gather feedback concerning the design and the lisp
> code.  Do we need ChangeLog patches as well to apply the patches to
> current emacs?  Right now I've not worked on updates to the gnus
> manual.

We don't need ChangeLog patches any more, but we generate
"ChangeLog-style" git commits instead.  Basically, just use `C-x 4 a',
and type in the change as usual, and then when checking in, vc-mode will
snarf those entries into the commit buffer.

> The first patch is against gssapi.el from Ma Gnus v0.15, the latest gnus
> release.  I've removed the options "--authentication-id" from gsasl and
> "-u" from imtest invocations.  If somebody needs these, we could add the
> user parameter back to open-gssapi-stream as an optional parameter.
> That way open-network-stream could still call open-gssapi-stream without
> changes, other users can pass a username.  I'm not sure if the username
> is really neded - my usecase works fine without.

There's no user name in the default gssapi-program, at least...

> If we don't want to add an optional parameter or need to pass the
> username from nnimap.el to network-stream.el and finally to gssapi.el,
> we could add a property like :gssapi-user to the call to
> open-network-stream and pass that to open-gssapi-stream.

It would be nice if we didn't, but that's a possibility.

> The second change is removing the call to erase buffer.  That way the
> function open-network-stream-gssapi in network-stream.el can fetch the
> greeting and capabilities string from the buffer.
>
> I currently know of one difference between gsasl and imtest: connections
> with gsasl use TLS, imtest doesn't.  If we want that, we can add '-t ""'
> to the imtest call according to the imtest manpage:
>
>        -t keyfile
>                      Enable TLS.  keyfile contains the TLS public and
>                      private keys.  Specify "" to negotiate a TLS
>                      encryption layer but not use TLS authentication.
>
> Another option could be to handle STARTTLS in
> network-stream-open-gssapi.  For my usecase I'll use gsasl, so I've not
> added code for that.

Hm...  it would have been nice if this all went through our normal TLS
functions, so that the user could be given the opportunity to use the
network security manager in Emacs, which handles certificate errors and
the like.  So I think it would be very nice if
network-stream-open-gssapi handled TLS itself.

> Any comments?

I think everything looked very nice.  :-)

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



  reply	other threads:[~2016-02-13  6:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-29 14:35 gssapi " 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
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 [this message]
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=87oablkss4.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).