[15836] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: Sanity check: GSSAPI SPI simplifications

daemon@ATHENA.MIT.EDU (Nicolas Williams)
Tue May 25 11:52:59 2010

Date: Tue, 25 May 2010 10:52:39 -0500
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: Tom Yu <tlyu@mit.edu>
Message-ID: <20100525155239.GB9605@oracle.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <ldvaarouh96.fsf@cathode-dark-space.mit.edu>
Cc: "krbdev@mit.edu" <krbdev@mit.edu>, Jeffrey Hutzelman <jhutz@cmu.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu

On Tue, May 25, 2010 at 11:35:01AM -0400, Tom Yu wrote:
> Nicolas Williams <Nicolas.Williams@oracle.com> writes:
> 
> > (Aside: I suspect that most mechglues will have sufficiently similar
> > SPIs that targeting multiple mechglues will generally be feasible.)
> 
> ...except that there is some disagreement about whether the GSS-API
> itself is a suitable SPI for a mechglue.

I used to be a strong proponent of the API as the SPI.  Now I think the
API is a good model for the SPI, but that the API as-is not good as the
SPI.  I'm not sure how much disagreement there is about this.

I'm glad that Greg asked though.  The SPI surely will someday be a
public interface, so even though it's private now evolution of it should
be subject to debate.  In this case I think the proposed evolution is
perfectly fine.

Nico
-- 
_______________________________________________
krbdev mailing list             krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

home help back first fref pref prev next nref lref last post