On Sat, Mar 08, 2003 at 11:37:35PM -0500, Adolfo Santiago wrote:
> If MD2 support is the issue (is it?), is there a way to tell nessus not to
> use it?

I fixed it in CVS. Here's the patch :


Index: nasl_init.c
===================================================================
RCS file: /usr/local/cvs/libnasl/nasl/nasl_init.c,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -d -r1.39 -r1.40
--- nasl_init.c 7 Mar 2003 14:01:56 -0000       1.39
+++ nasl_init.c 9 Mar 2003 12:03:28 -0000       1.40
@@ -243,7 +243,9 @@
   "SHA", nasl_sha, 1, { NULL },
   "SHA1", nasl_sha1, 1, { NULL },
   "RIPEMD160", nasl_ripemd160, 1, { NULL },
+#ifdef HAVE_OPENSSL_MD2_H  
   "HMAC_MD2", nasl_hmac_md2, 0, { "data", "key", NULL },
+#endif  
   "HMAC_MD5", nasl_hmac_md5, 0, { "data", "key", NULL },
   "HMAC_SHA", nasl_hmac_sha, 0, { "data", "key", NULL },
   "HMAC_SHA1", nasl_hmac_sha1, 0, { "data", "key", NULL },

Index: nasl_crypto.h
===================================================================
RCS file: /usr/local/cvs/libnasl/nasl/nasl_crypto.h,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- nasl_crypto.h       7 Mar 2003 14:01:56 -0000       1.6
+++ nasl_crypto.h       9 Mar 2003 12:03:28 -0000       1.7
@@ -16,7 +16,9 @@
 
 tree_cell * nasl_ripemd160(lex_ctxt *);
 
+#ifdef HAVE_OPENSSL_MD2_H
 tree_cell * nasl_hmac_md2(lex_ctxt * );
+#endif
 tree_cell * nasl_hmac_md5(lex_ctxt * );
 tree_cell * nasl_hmac_sha(lex_ctxt *);
 tree_cell * nasl_hmac_sha1(lex_ctxt * );

Index: nasl_crypto.c
===================================================================
RCS file: /usr/local/cvs/libnasl/nasl/nasl_crypto.c,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- nasl_crypto.c       7 Mar 2003 14:01:56 -0000       1.9
+++ nasl_crypto.c       9 Mar 2003 12:03:28 -0000       1.10
@@ -217,11 +217,12 @@
 }
 
 
-
+#ifdef HAVE_OPENSSL_MD2_H
 tree_cell * nasl_hmac_md2(lex_ctxt * lexic)
 {
  return nasl_hmac(lexic, EVP_md2());
 }
+#endif
 
 tree_cell * nasl_hmac_md5(lex_ctxt * lexic)
 {


Reply via email to