> De: TAKAHASHI Hideo(BSD-M1G) [mailto:[EMAIL PROTECTED]]
> Enviado el: jueves 28 de febrero de 2002 3:00
> I took a further look into msdn and found something that might help.
>
> I will try this if I can find some time...
OK, i think you've found the infos needed to do the job..
I you last
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
> 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 in
print : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>-Original Message-
>From: TAKAHASHI Hideo(BSD-M1G) [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, February 27, 2002 3:12 AM
>To: [EMAIL PROTECTED]
>Subject: obtaining cipher suite within an isapi extension
>
>
>Hello.
>
Hello.
I am currently trying to test 4.0.2 behind IIS on Win2K, via ajp13,
and I'm trying out the SSL features.
I found that the cipher suite string is not passed from IIS to jk and
I want to know if the implementation is merely not yet done, or if
there are technical reasons that makes the task
