Re: SASL 2.1.27 rc8

Quanah Gibson-Mount <[email protected]> Tue, 18 Sep 2018 08:05:48 -0700
Newsgroups gmane.comp.security.cyrus.sasl
Message-ID <73D508D78D1CBDBE76F5A285@[192.168.1.39]>
--On Tuesday, September 18, 2018 11:10 AM -0400 Ken Murchison 
<[email protected]> wrote:

>
> I want to get 2.1.27 released this week, but I'm not sure where we stand
> with the GSSAPI stuff, and since I'm no longer at CMU, I don't have a
> Kerberos infrastructure to test with.
>
> So, I need someone to summarize the existing problem(s) and solution(s),
> preferably with a pull request or patch.

Hi Ken,

On GSSAPI: There is no mechanism in Heimdal to allow for pulling the SSF 
level for a Kerberos mechanism (only exists in MIT).  I've opened an issue 
on the Heimdal side for this, but I wouldn't hold the release on this.  I 
don't have an MIT environment, so someone else would need to confirm the 
SSF bits (no more hard coded "56" with GSSAPI, for example) are working 
correctly.

Otherwise, there are several pull requests fixing issues with building the 
last RC:

<https://github.com/cyrusimap/cyrus-sasl/pull/532>
<https://github.com/cyrusimap/cyrus-sasl/pull/530>
<https://github.com/cyrusimap/cyrus-sasl/pull/529>
<https://github.com/cyrusimap/cyrus-sasl/pull/527>

--Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>