OK, there's at least one application author who has provided dynamic locking
callbacks
This commit is contained in:
parent
d64b16ab25
commit
04c71cd725
4
CHANGES
4
CHANGES
@ -5,8 +5,8 @@
|
|||||||
Changes between 0.9.6h and 0.9.7 [XX xxx 2002]
|
Changes between 0.9.6h and 0.9.7 [XX xxx 2002]
|
||||||
|
|
||||||
*) The hw_ncipher.c engine requires dynamic locks. Unfortunately, it
|
*) The hw_ncipher.c engine requires dynamic locks. Unfortunately, it
|
||||||
seems that in spite of existing for more than a year, no application
|
seems that in spite of existing for more than a year, many application
|
||||||
author has done anything to provide the necessary callbacks, which
|
author have done nothing to provide the necessary callbacks, which
|
||||||
means that this particular engine will not work properly anywhere.
|
means that this particular engine will not work properly anywhere.
|
||||||
This is a very unfortunate situation which forces us, in the name
|
This is a very unfortunate situation which forces us, in the name
|
||||||
of usability, to give the hw_ncipher.c a static lock, which is part
|
of usability, to give the hw_ncipher.c a static lock, which is part
|
||||||
|
Loading…
x
Reference in New Issue
Block a user