On Fri, Nov 28, 2008 at 1:54 PM, Fastream Technologies
<[EMAIL PROTECTED]>wrote:

> Ok, that's what I assumed but the code below fails:
>
>   HTTPSSLContext->SslOptions >> sslOpt_NO_SSLv2 >> sslOpt_NO_SSLv3 >>
> sslOpt_NO_TLSv1;
>   if(!useSSLv2)
>    HTTPSSLContext->SslOptions << sslOpt_NO_SSLv2;
>   if(!useSSLv3)
>    HTTPSSLContext->SslOptions << sslOpt_NO_SSLv3;
>   if(!useTLSv1)
>    HTTPSSLContext->SslOptions << sslOpt_NO_TLSv1;
> What's wrong with this?
>
> Regards,
> SZ
>   On Fri, Nov 28, 2008 at 1:48 PM, Arno Garrels <[EMAIL PROTECTED]>wrote:
>
>> Fastream Technologies wrote:
>> > Please let all of us know as this is important for PCI DSS compliance.
>>
>> Set SslVersionMethod of the SslContext to either sslV23_CLIENT or
>> sslV23_Server and add sslOpt_NO_SSLv2 to the SslOptions.
>>
>> --
>> Arno Garrels [TeamICS]
>> http://www.overbyte.be/eng/overbyte/teamics.html
>>
>> --
>>
>


-- 
Gorkem Ates
Fastream Technologies
Software IQ: Innovation & Quality
www.fastream.com | Email: [EMAIL PROTECTED] | Tel: +90-312-223-2830 |
MSN: [EMAIL PROTECTED]
Join IQWF Server Yahoo group at http://groups.yahoo.com/group/IQWFServer
Join IQ Reverse Proxy Yahoo group at
http://groups.yahoo.com/group/IQReverseProxy
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to