Fix a number of ASN1_INTEGER vs ASN1_STRING mixups coming from the

mechanical M_ASN1 macro expansion.  The ASN1_INTEGER_cmp function
takes signs into account while ASN1_STRING_cmp doesn't. The mixups
mostly involve serialNumbers, which, in principle, should be positive.
However, it is unclear whether that is checked or enforced anywhere
in the code, so these are probably bugs.

Patch from Holger Mikolon
ok jsing

1 files changed, 2 insertions, 2 deletions

diff --git a/src/lib/libcrypto/pkcs7/pk7_doit.c b/src/lib/libcrypto/pkcs7/pk7_doit.c
index 24ab957b4c..d0c27e98a9 100644
--- a/src/lib/libcrypto/pkcs7/pk7_doit.c
+++ b/src/lib/libcrypto/pkcs7/pk7_doit.c
@@ -1,4 +1,4 @@
-/* $OpenBSD: pk7_doit.c,v 1.42 2017/05/02 03:59:45 deraadt Exp $ */
+/* $OpenBSD: pk7_doit.c,v 1.43 2019/03/13 20:34:00 tb Exp $ */
 /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
  * All rights reserved.
  *
@@ -410,7 +410,7 @@ pkcs7_cmp_ri(PKCS7_RECIP_INFO *ri, X509 *pcert)
             pcert->cert_info->issuer);
         if (ret)
                 return ret;
-        return ASN1_STRING_cmp(pcert->cert_info->serialNumber,
+        return ASN1_INTEGER_cmp(pcert->cert_info->serialNumber,
             ri->issuer_and_serial->serial);
 }