[17250] in Kerberos_V5_Development
Re: GSS memory allocation initial cut for review
daemon@ATHENA.MIT.EDU (Nico Williams)
Wed Oct 5 12:05:29 2011
MIME-Version: 1.0
In-Reply-To: <tslk48jv4wi.fsf@mit.edu>
Date: Wed, 5 Oct 2011 11:02:52 -0500
Message-ID: <CAK3OfOgYXo0CkPh7R0yL0m2T-SzO_3VbzbHOiLUqYjzT+j8B3w@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Sam Hartman <hartmans@painless-security.com>
Cc: kevin.wasserman@painless-security.com, krbdev@mit.edu
Content-Type: text/plain; charset="utf-8"
Errors-To: krbdev-bounces@mit.edu
Content-Transfer-Encoding: 8bit
On Wed, Oct 5, 2011 at 10:23 AM, Sam Hartman<hartmans@painless-security.com> wrote:> We've said that we will post on kitten. Our claim is that having all> allocations in MIT's mechglue go through one allocation function is an> MIT matter and changing what that allocation function does on windows is> not that hard to do.
For any one mechglue implementors are free to do as they wish. But Ithought you wanted all mechglues on a platform to share an allocator,and *that* would require some consensus among implementors.
Nico--
_______________________________________________krbdev mailing list krbdev@mit.eduhttps://mailman.mit.edu/mailman/listinfo/krbdev
