You are using the correct API. Read the documentation. The API will tell you the size of the memory you need to allocate.

Manoj Mohan wrote:

Yeah thats true.. so how do I ensure that it works generically. I was hoping to call some API which will help me to do that.
Is there one ?

Manoj
Inactive hide details for Jeffrey Altman <[EMAIL PROTECTED]>Jeffrey Altman <[EMAIL PROTECTED]>


                        *Jeffrey Altman <[EMAIL PROTECTED]>*

                        01/28/2008 02:40 PM
                        Please respond to
                        [EMAIL PROTECTED]

        

To
        
Manoj Mohan/Lenexa/[EMAIL PROTECTED]

cc
        
kerberos@mit.edu

Subject
        
Re: SSPI API to get tokensize for client and server

        


that code will only work if the generated token is 4096 bytes or smaller.

Manoj Mohan wrote:
> Hi,
>
> Right now I am calling InitializeSecurityContext and AcceptSecurityContext
> with fixed token size (4096)
> and things are working. I was wondering if I can call
> QueryContextAttributes or some other function
> to get the right value rather than using a fixed value?
>
> For example, I am using using AcceptSecurityContext like this:
>
> ....................
>   outBuffer.cbBuffer = 4096;
>   outBuffer.BufferType = SECBUFFER_TOKEN;
>   outToken.ulVersion = SECBUFFER_VERSION;
>   outToken.cBuffers = 1;
>   outToken.pBuffers = &outBuffer;
>
>   ss = AcceptSecurityContext( pCredHandle,
>                               pInCtxHandle,
>                               &inToken,
>                               NULL,
>                               SECURITY_NATIVE_DREP,
>                               pOutCtxHandle,
>                               &outToken,
>                               &outFlags,
>                               &lifetime );
>   if( ss != SEC_E_OK )
> .................................
>
> Regards,.........................
> Manoj
> ________________________________________________
> Kerberos mailing list           Kerberos@mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

Reply via email to