El 09/08/12 15:20, Luke Howard escribió:
> On 09/08/2012, at 10:55 PM, Alejandro Perez Mendez <[log in to unmask]> wrote:
>
>> Actually, I'm thinking now that it could be easier to just insert the whole exported context into the authorization_data, instead of inserting the attributes, in such a way that the TGS will be able to reconstruct the state and access to the attributes directly using GSS functions. This would avoid me the problem with "framing" the authorization_data in order to encode the attributes (it wouldn't be difficult, though). Hence, I could call the authorization_data element "GssContext" instead of "GssAttributes".
> If you want a serialised attribute list, call gss_export_name_composite() on the initiator name. You can place that in the authorisation data and import it later.
>
> (GSS_C_NT_COMPOSITE_EXPORT doesn't exist yet [we should fix this if naming extensions has been published?] but GSS_C_NT_EXPORT_NAME will work for importing a composite name.)
You know, right after sending the email, on my way home, I was thinking
that there should be a call to do exactly that, export a composite name
:). Thank's for remind me. I will use that since I don't need the whole
context.
Regards,
Alejandro
> -- Luke
|