GSS memory allocation initial cut for review
hartmans at painless-security.com
Wed Oct 5 13:15:56 EDT 2011
>>>>> "Nico" == Nico Williams <nico at cryptonector.com> writes:
Nico> On Wed, Oct 5, 2011 at 10:23 AM, Sam Hartman
Nico> <hartmans at 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.
Nico> For any one mechglue implementors are free to do as they wish.
Nico> But I thought you wanted all mechglues on a platform to share
Nico> an allocator, and *that* would require some consensus among
I do, but my timely pressing concern is the changes to the MIT code.
For now we're calling heapalloc. But if the consensus is something else
and we've made changes to run allocations through one place it's easy to
match that consensus.
We presented the long-term plan only for context; the long-term
discussion needs to happen on kitten.
I've said this several times both on krbcore and krbdev.
Well, OK, I may have only said it once on krbdev, but that was in the
More information about the krbdev