[45] in GSSAPI Development

home help back first fref pref prev next nref lref last post

RE: FWD: [ clarification on GSS C Bindings ] -- in case you haven't seen this

daemon@ATHENA.MIT.EDU (John Wray, Secure Systems Developm)
Thu May 16 18:39:29 1991

Date: Thu, 16 May 91 15:37:14 PDT
From: "John Wray, Secure Systems Development, DTN 226-6106  15-May-1991 0950" <wray@ultra.enet.dec.com>
To: sejour::kannan@zendia.enet.dec.com

Thanks, I didn't get this message - is the problem at our end?

>Why is the desired_name passed in to gss_acquire_cred of type gss_name_t?
>Don't we want to use gss_buffer_t?

The desired_name parameter is a global principal name (the name of the
principal whose credentials you want to acquire), and should therefore use the
gss_name_t type.

>Also, shouldn't the output_token argument for init_context and accept_context
>be of type (gss_buffer_t *)?

Allocation of the gss_buffer_desc object is the responsibility of the caller
(section 2.1.3);  Thus a gss_buffer_t value is passed in telling the routine
where the buffer descriptor is.  The API routine will allocate space for the
token, and fill in the fields of the buffer descriptor accordingly.

John

home help back first fref pref prev next nref lref last post