[krbdev.mit.edu #5233] Change in behaviour in gss_release_buffer() by mechtypes introduces memory leak

[Ezra Peisach via RT]

Sam Hartman via RT wrote:
> Note that callers should not be releasing buffers that they allocated.
> So I think we need only be consistent within our implementation and
> within mechanisms that plug into our implementation.
>
>   
Exactly....  The mechanism interface has changed the implementation 
requirements.  The release_buffer is not passed down to the mech 
specific handlers.  So - self consistency in the implementation would 
now require a change in the k5sealv3.c code...

Ezra