From owner-freebsd-ports-bugs@freebsd.org Sat Apr 29 13:19:24 2017 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3E96D553A9 for ; Sat, 29 Apr 2017 13:19:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB109A9E for ; Sat, 29 Apr 2017 13:19:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3TDJOq4045398 for ; Sat, 29 Apr 2017 13:19:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 218899] mail/mutt GSSAPI oddity Date: Sat, 29 Apr 2017 13:19:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: mason@blisses.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Apr 2017 13:19:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218899 --- Comment #7 from Mason Loring Bliss --- On Fri, Apr 28, 2017 at 11:51:08PM +0000, bugzilla-noreply@freebsd.org wrot= e: > However, I'd like to guess without GSSAPI_* selected this disables mutt's > ability to authenticate directly with IMAP servers with GSSAPI. But if SA= SL > 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= =20 didn't try to authenticate using GSSAPI itself, and evidently shoved it off= =20 to the SASL code. When that failed, it didn't try to authenticate using=20 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=20 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 wi= th GSSAPI until I popped in the cyrus-sasl-gssapi package, so its native GSSAPI code path was evidently never tried. --=20 Mason Loring Bliss mason@blisses.org http://blisses.org/=20= =20 "I am a brother of jackals, and a companion of ostriches." (Job 30 : 29) --=20 You are receiving this mail because: You are the assignee for the bug.=