all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Request for advice on GNUS internals. GSSAPI progress report
Date: Tue, 28 Feb 2017 15:25:21 +0800	[thread overview]
Message-ID: <CADtN0WJq444D9wtz54T-O1PYU-2Lry9mG4kP6Oe03uwA+vR_qg@mail.gmail.com> (raw)
In-Reply-To: <m360jvha1o.fsf@stories>

[-- Attachment #1: Type: text/plain, Size: 2520 bytes --]

On 28 February 2017 at 00:29, Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Elias Mårtenson <lokedhs@gmail.com> writes:
>
> > I don't know about POP3, does anyone still use that? It's definitely
> > supported for SMTP, and now that you mention it, I have to implement
> > that support too. It would be a pretty useless feature if you can read
> > your mail without requiring a stored password, but still needing it to
> > send them. :-)
>
> If this is relevant to a lot of the different protocols, perhaps it
> would make more sense to put this into the Emacs core like the TLS
> support?  Then each protocol wouldn't have to be modified this much to
> support it across Emacs...


Unfortunately, that's not possible. Every protocol has a different idea how
to perform a GSSAPI handshake. GSSAPI itself only returns a binary blong
that is to be sent to the remote side, that side can then send another blob
back. After ping-ponging a few times, you get a validated name object
representing the remote principal, and context that can be used to encrypt
and decrypt other binary blobs. There docs literally says something along
the lines of: “Send the binary output to the remote server and pass it to
gss_accept_sec_context()”.

This results in plenty of different specs how to apply GSSAPI
authentication to various protocols. A few examples:

  - IMAP: https://tools.ietf.org/html/rfc1731
  - SMTP: https://tools.ietf.org/html/rfc4954
  - POP3: https://tools.ietf.org/html/rfc5034
  - LDAP: https://tools.ietf.org/html/rfc4752

Etc, etc.

Currently, when using GNUS, LDAP authentication works with GSSAPI thanks to
fact that Emacs leverages the ‘ldapsearch’ external program. IMAP4 works
now because I've implemented it. I don't use POP3, and I don't think there
is much demand for it.

That leaves SMTP, which really should have support in Gnus proper, but as
it turns out, we're not using authenticated SMTP at my workplace so I'll
have a hard time testing it. The same goes for encrypted IMAP (using GSS
encryption, rather than tunnelling over TLS). To support it, one would have
to implement a very simple function but I left that empty since I have no
way of testing it.

So, that's the situation as it stands. I've restarted the process with my
employer's legal team to make sure I can get the copyright assignments
done. It seems to actually be happening this time (which means that we'll
be able to get gnu-apl-mode into ELPA soon).

Regards,
Elias

[-- Attachment #2: Type: text/html, Size: 3379 bytes --]

  reply	other threads:[~2017-02-28  7:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  4:37 Request for advice on GNUS internals. GSSAPI progress report Elias Mårtenson
2017-02-15 10:13 ` Elias Mårtenson
2017-02-16 10:17   ` Elias Mårtenson
2017-02-20 16:10     ` Lars Ingebrigtsen
2017-02-21  2:50       ` Elias Mårtenson
2017-02-21  3:42         ` Eli Zaretskii
2017-02-21  4:50           ` Elias Mårtenson
2017-02-21  8:00         ` Michael Albinus
2017-02-27 16:29         ` Lars Ingebrigtsen
2017-02-28  7:25           ` Elias Mårtenson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-16 15:42 Live System User
     [not found] ` <CADtN0W+AdbL9xo2_M-bfV3K=Xsu5-puUJ1bA3aw_=KMT6hSv5w@mail.gmail.com>
     [not found]   ` <CADtN0WLv9v57Di8O66Ggxo8Gk6Hi50OykK=J5UMTqCiOpROn-A@mail.gmail.com>
2017-02-16 16:09     ` Elias Mårtenson

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=CADtN0WJq444D9wtz54T-O1PYU-2Lry9mG4kP6Oe03uwA+vR_qg@mail.gmail.com \
    --to=lokedhs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.