Last post Aug 27, 2016 06:28 PM by PatriceSc
Aug 24, 2016 02:00 AM|snowfrost88|LINK
I have a webservice and I am the consumer. Currently, my webservice failed to do the SSL handshake due to ciphers failure. I have already set the AES ciphers at my server registry but when I run Wireshark software to trace the network traffic, it can't
detect the AES ciphers in the server. Do I have to set to read what cipher in your application source ? Or is there anywhere I need to set at the server to read the AES ciphers? I am using Microsoft Server 2003.
Appreciate help in this. Thank Yoi.
Aug 24, 2016 08:34 AM|PatriceSc|LINK
Could it be that it is not supported out of the box in Windows Server 2003 ? I found
https://support.microsoft.com/en-us/kb/948963. Try first maybe a Windows admin group to check which support you have for this in 2003 ?
Aug 24, 2016 09:15 AM|snowfrost88|LINK
I have installed the hotfix as what you have given in the above URL but my application failed to read the ciphers.
This is what is reflected in my server 's registry:
AES 128/128 ->Set to enabled
AES 256/256 ->Set to enabled
DES 56/56->Set to enabled
RC2 128/128->Set to enabled
RC2 40/128->Set to enabled
RC4 128/128->Set to enabled
RC4 40/128->Set to enabled
RC4 56/128->Set to enabled
TLS_RSA_WITH_AES_128_CBC_SHA ->Set to enabled
TLS_RSA_WITH_AES_256_CBC_SHA ->Set to enabled
Triple DES 168/168->Set to disabled
Aug 27, 2016 06:28 PM|PatriceSc|LINK
And so the error is ? Maybe you could try
https://www.ssllabs.com/ssltest/ which should help to understand what is available. It seems the needed cipher is still not available. BTW 2003 is outdated. Do you consider to upgrade?