I took a further look into msdn and found something that might help. You cannot get the cipher string directly, but it seems you can reach some equivalent information.
1. call lpEcb->ServerSupportFunction() for HSE_REQ_GET_SSPI_INFO. SSPI is for security support provider interface. That will get you a CtxtHandle (context handle) which leads you to detailed info about the connection that is established. 2. call QueryContextAttribute on that CtxtHandle to get SECPKG_ATTR_CONNECTION_INFO. This will give you a struct named _SecPkgContext_ConnectionInfo. On that struct you will find values that are chosen from constants like SP_PROT_SSL3_SERVER, CALG_DES, CALG_SHA, CALG_RSA_KEYX. Sounds quite close to what we want now. Then you can combine these info to produce the cipher suite string by yourself. Obviously not the best way, but it might work. I will try this if I can find some time... "Ignacio J. Ortega" wrote: > > > De: TAKAHASHI Hideo(BSD-M1G) [mailto:[EMAIL PROTECTED]] > > Enviado el: miércoles 27 de febrero de 2002 3:12 > > > within an ISAPI extension. My guess is that there is no easy way to > > do this, and I want to know if anyone tried this job and reached any > > conclusions. > > As Henri points, i did that initial IIS docs digging when we implemented > the SSL support for isapi_connector in 3.3, and AFAIK this information > is not easy to be derived from the information present to a Filter DLL., > nor to a Extension DLL.., just now i'm deep on other worlds ( much more > sided to my monthly paycheck :), but i can try to redig my way there and > let you know which was the wall i hit in my past research.. > > Any help is welcomed,.. > -- Hideo Takahashi Business Solutions Division, Hitachi Ltd. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
