Sanity check: GSSAPI SPI simplifications
Love Hörnquist Åstrand
lha at kth.se
Mon May 24 21:13:35 EDT 2010
24 maj 2010 kl. 15:49 skrev Jeffrey Hutzelman:
> So, this would make the krb5 mech no longer be a GSS-API implementation.
> I suppose that's OK, if you assume that your mech is only ever going to be
> used with your mechglue. The problem is that as soon as more than one
> implementor makes that assumption, you stop being able to use arbitrary
> sets of mechanisms -- you can only use sets of mechanisms for which there
> is a mechglue with which they are all compatible.
> What if I want to use your mechanism, but my OS/application/whatever
> already has its own mechglue? What if I am building an application that I
> know needs only krb5 and has to run in limited space?
All good points, however duplicating code is multiple layers hides bugs and increases code size, either good either.
More information about the krbdev