Dr. Stephen Henson wrote:
On Wed, Jan 07, 2009, Victor Duchovni wrote:This is not very clear to me. Which signatures are poorly verified: 1. The server's signature on SSL/TLS protocol messages that must be signed under the server's private key (corresponding to the private key in its certificate)?[ITYM "... corresponding to the public key in its certificat..."] Yes it is 1 only. Certificate chain validation is not affected nor other forms of DSA/ECDSA signature verification such as S/MIME.
Stephen, can you elaborate on that response because from the patch it seems that more than only client validation of the server signature in SSL sessions is affected.
cms/cms_sd.c is affected, but the consequence is only a missing error message, right ?
ssl/s2_srvr.c ssl/s3_srvr.c : The error in those two file seems to mean that server verification of DSA signed clients certificates is also affected.
apps/verify.c is affected. This is the "app" file, not "crypto", so chain validation that is done in crypto is not affected. But if someone happens to rely on the command line tool to do the verification, he may be affected.
apps/spkac.c is affected. This will not impact many people (command line verification of Netscape format certificate request) but should be noted.
apps/x509.c is affected, but the impact seems extremely low affecting only the code path to generate a self signed cert.
Also it may be important to insist on the point that anybody who has developed applications using openssl and using the existing code as a model (cut/paste) is quite likely to be impacted by this problem.
______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
