[17240] in Kerberos_V5_Development
Re: GSS memory allocation initial cut for review
daemon@ATHENA.MIT.EDU (Kevin Wasserman)
Sat Oct 1 16:20:48 2011
Message-ID: <SNT101-DS16F9C8C8DBAC628B316B1FB5F40@phx.gbl>
From: "Kevin Wasserman" <krwasserman@hotmail.com>
To: <jaltman@secure-endpoints.com>, <krbdev@mit.edu>
In-Reply-To: <4E848CD1.9080101@secure-endpoints.com>
Date: Sat, 1 Oct 2011 16:20:45 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
Apologies for the delay getting back to you on this...
I agree with you that getting a uniform gss mechglue
specification that that included a context passed in
every call would be a vast improvement over the
current mechglue situation. Unfortunately it would
also be a serious undertaking that would impact every
platform, not just windows. I believe such an effort
is beyond the scope of our current projects and I do
not think it is strict requirement. It's possible I could
be proven wrong. I'm not sure what you mean by
"...Moonshot requires that mechglue layers themselves
be mechanisms". I'm not aware of any such requirement.
Sam is incommunicado until Monday, but perhaps he
can shed more light when he returns. I'm loath to
get into any detail about Moonshot myself both
because it's out of scope for this list and because
I don't know the project well enough to trust myself
to be completely accurate.
-Kevin Wasserman
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
