Re: WG Last Call: draft-ietf-sasl-gs2-14

[Simon Josefsson <simon@xxxxxxxxxxxxx>]

Alexey Melnikov <alexey.melnikov@xxxxxxxxx> writes:

>>>>Do the 3 output parameters need to be freed?
>>>>      
>>>>
>>>Not sure if this needs to be mentioned, I can't find much discussion in
>>>RFC 2743 on this.  Nico?
>>>    
>>>
>>Things that are constant-like don't need to be freed.  For example,
>>mechanism OIDs returned by GSS_Indicate_mechs(),
>>GSS_Inquire_sec_context(), ...
>>
>>The same should apply here to these three output arguments.
>>
>>Yes, that means that if an implementation were to malloc memory for
>>them, then it could only freed them when the shared object is unloaded
>>or the process exits.
>>  
>>
> This is fine with me. I would recommend adding this to the document.

Is my proposal to add

   The memory allocated for the output variables must not be released
   by the application.

OK?  (Note I changed "should" into "must" here.)

My text takes care of guidance for application writers, which I think is
more important.  What Nico wrote is guidance for GSS-API authors.  Text
proposals welcome to add that welcome. ;)

/Simon