In 0.9.8a, it looks like AES 128 will be accepted by the server even if it is supposed to accept only AES 256.
To reproduce this behavior, on the server run:
openssl s_server -accept 4433 -cipher AES256-SHA –state
On the client, run:
openssl s_client -connect PISA_SERVER:4433 -cipher AES128-SHA
Sorry, I somehow overlooked that previous thread. Note that in my
scenario, a weaker cipher is implicitly added to the supported cipher
list, so the bug is somewhat more severe IMHO.
What I tried was to remove all the AES 128 options from ssl/s3_lib.c.
That seemed to do the trick. I do not know
