This one deserves a note. In the change to CHANGES, there's the

following:

+     NOTE: This is for the 0.9.7 series ONLY.  This hack will never
+     appear in 0.9.8 or later.  We EXPECT application authors to have
+     dealt properly with this when 0.9.8 is released (unless we actually
+     make such changes in the libcrypto locking code that changes will
+     have to be made anyway).

That makes this one a false positive.

diff --git a/ChangeLog.0_9_7-stable_not-in-head b/ChangeLog.0_9_7-stable_not-in-head
index 93d524b117d47d0f6ef71e04a929cc73d7b0fe34..6b3ff3b0151181bfe5b6fb56fa926586bcbae1bc 100644 (file)
--- a/ChangeLog.0_9_7-stable_not-in-head
+++ b/ChangeLog.0_9_7-stable_not-in-head
@@ -40,20 +40,6 @@ be added to the end of this file.
        Return my normal debug targets to something not so extreme, and
        make the extreme ones special (or 'extreme', if you will :-)).
 
-2002-12-12 18:41  levitte
-
-       Changed:
-               crypto/engine/hw_ncipher.c (1.26.2.7), "Exp", lines: +38 -2
-               crypto/engine/hw_ncipher_err.c (1.1.2.2), "Exp", lines: +1 -1
-               crypto/engine/hw_ncipher_err.h (1.1.2.2), "Exp", lines: +1 -1
-               crypto/cryptlib.c (1.32.2.8), "Exp", lines: +2 -1
-               crypto/crypto.h (1.62.2.7), "Exp", lines: +2 -1
-               CHANGES (1.977.2.78), "Exp", lines: +14 -0
-
-       Add a static lock called HWCRHK, for the case of having an
-       application that wants to use the hw_ncipher engine without having
-       given any callbacks for the dynamic type of locks.
-
 2002-12-15 16:27  appro
 
        Changed: