The failure is due to difference in prototypes of int_rsa_verify in
rsa_locl.h and rsa_sign.c.  The patch also eliminates a warning of
similar nature in s_server.c.

Index: apps/s_server.c
===================================================================
RCS file: /cvs-openssl/openssl/apps/s_server.c,v
retrieving revision 1.115
diff -u -r1.115 s_server.c
--- apps/s_server.c     17 Apr 2006 12:22:13 -0000      1.115
+++ apps/s_server.c     5 Sep 2006 14:54:55 -0000
@@ -313,7 +313,7 @@
                goto out_err;
                }
        if (s_debug)
-               BIO_printf(bio_s_out,"identity_len=%d identity=%s\n",
+               BIO_printf(bio_s_out,"identity_len=%lu identity=%s\n",
                        identity ? strlen(identity) : 0, identity);
 
        /* here we could lookup the given identity e.g. from a database */
Index: crypto/rsa/rsa_sign.c
===================================================================
RCS file: /cvs-openssl/openssl/crypto/rsa/rsa_sign.c,v
retrieving revision 1.27
diff -u -r1.27 rsa_sign.c
--- crypto/rsa/rsa_sign.c       5 Sep 2006 08:58:03 -0000       1.27
+++ crypto/rsa/rsa_sign.c       5 Sep 2006 14:54:55 -0000
@@ -144,9 +144,9 @@
        }
 
 int int_rsa_verify(int dtype, const unsigned char *m,
-                         unsigned int m_len,
-                         unsigned char *rm, unsigned int *prm_len,
-                         const unsigned char *sigbuf, unsigned int siglen,
+                         size_t m_len,
+                         unsigned char *rm, size_t *prm_len,
+                         const unsigned char *sigbuf, size_t siglen,
                          RSA *rsa)
        {
        int i,ret=0,sigtype;


-- 
Artem Chuprina
RFC2822: <ran{}ran.pp.ru> Jabber: [EMAIL PROTECTED]

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [email protected]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to