Fastream Technologies wrote:
> It did not work!
Peers exchange cipher suits in plain text during the SSL
handshake so it's possible to check whether one peer might
sent only a few, weak ciphers using a protocol analizer.
If I recall it well, by default clients select the cipher
for the session.
It did not work!
On Sat, Nov 28, 2009 at 1:12 PM, Fastream Technologies
wrote:
> I thought it was the default setting.
>
> On Sat, Nov 28, 2009 at 12:00 PM, Arno Garrels
> wrote:
> > Fastream Technologies wrote:
> >> I forgot to say: useSSLv2 is off and the other two is on in flags.
> >
> > Did
I thought it was the default setting.
On Sat, Nov 28, 2009 at 12:00 PM, Arno Garrels wrote:
> Fastream Technologies wrote:
>> I forgot to say: useSSLv2 is off and the other two is on in flags.
>
> Did you try sslOpt_CIPHER_SERVER_PREFERENCE yet?
>
> --
> Arno Garrels
>
>
> --
> To unsubscribe or
Fastream Technologies wrote:
> I forgot to say: useSSLv2 is off and the other two is on in flags.
Did you try sslOpt_CIPHER_SERVER_PREFERENCE yet?
--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/tws
I forgot to say: useSSLv2 is off and the other two is on in flags.
Regards,
SZ
On Thu, Nov 26, 2009 at 10:16 AM, Fastream Technologies
wrote:
> Hello,
>
> I received the below message today:
>>Security test for PCI compliance is failing because of weak ciphers on the
>>proxy server. Cipher " D
Hello,
I received the below message today:
>Security test for PCI compliance is failing because of weak ciphers on the
>proxy server. Cipher " DES-CBC-SHA", description "Key Exchange: RSA;
>Authentication: RSA; Encryption: DES(56); MAC: SHA1" shows up in the proxy
>server only.
In the code,
HT
