[Bug 218899] mail/mutt GSSAPI oddity

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Apr 29 13:19:24 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218899

--- Comment #7 from Mason Loring Bliss <mason at blisses.org> ---
On Fri, Apr 28, 2017 at 11:51:08PM +0000, bugzilla-noreply at freebsd.org wrote:

> However, I'd like to guess without GSSAPI_* selected this disables mutt's
> ability to authenticate directly with IMAP servers with GSSAPI. But if SASL
> is enabled mutt will attempt to use SASL with cyrus-sasl via the
> cyrus-sasl-gssapi plugin will attempt to authenticate with GSSAPI. This
> would move the GSSAPI code from mutt to cyrus-sasl and its plugins?

That would match the behaviour I saw - even with GSSAPI_BASE selected, Mutt 
didn't try to authenticate using GSSAPI itself, and evidently shoved it off 
to the SASL code. When that failed, it didn't try to authenticate using 
GSSAPI itself. Maybe this is a bug in Mutt, not our packaging of it...?

> I'm unsure if you tested this from comment 0 but does GSS authentication
> work if you disable SASL and enable a compatible GSS implementation with
> mail/mutt?

I haven't tested this yet, but I will later today, and I'll report back 
within 12 hours of my submitting this comment.

> If you've only tested with the default options or the FreeBSD repo package
> then I would like to guess mutt would never attempt to try GSSAPI directly
> since --with-gss (Compile in GSSAPI authentication for IMAP) wouldn't be
> set at compile time.

No, I tested with GSSAPI_BASE as well, and I wasn't able to authenticate with
GSSAPI until I popped in the cyrus-sasl-gssapi package, so its native GSSAPI
code path was evidently never tried.

-- 
 Mason Loring Bliss         mason at blisses.org        http://blisses.org/  
"I am a brother of jackals, and a companion of ostriches."  (Job 30 : 29)

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list