SSPI API to get tokensize for client and server

Jeffrey Altman jaltman at secure-endpoints.com
Mon Jan 28 15:40:36 EST 2008


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 at mit.edu
> https://mailman.mit.edu/mailman/listinfo/kerberos
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3355 bytes
Desc: S/MIME Cryptographic Signature
Url : http://mailman.mit.edu/pipermail/kerberos/attachments/20080128/e0951d8b/attachment.bin


More information about the Kerberos mailing list