Hi Bolivar,
Ciphering is something done at the network level when the connection is
done. It is done exactly at the negotiation of the SSL session and it is
done by the Server (Apache, IIS, ...). So you can use the information
provided by the CGI Environment Variables of Apache (if it happens that
you are using Apache) to determine the actual SSL enc method.
More precisely you can use the HTTPS_CIPHER, HTTPS_KEYSIZE and
HTTPS_SECRETKEYSIZE to determine the different aspects of the actual
encryption method used by the client. If you want 128bits that means
Triple-DES for simetric encryption. If you do not have a strong know-how
at SSL I recommend you these two links:
Intro to SSL
http://developer.netscape.com/docs/manuals/security/sslin/index.htm
Apache-SSL doc
http://www.apache-ssl.org/docs.html
Hope this helps you.
Sean C. McCarthy
SCI, S.L. (www.sci-spain.com)
Bolivar Shagnasty wrote:
>
> My web site it going to be the starting point with a link to an application
> that only works with browser at 128bit strength. What I would like to do is
> automatically determine if the user doesn't have a compatible browser and
> then direct them where to get the correct browser. Does anyone know how I
> might go about doing this?
>
> tia,
> bol
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> To contact the list administrators, e-mail: [EMAIL PROTECTED]
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
