- 28 2月, 2002 2 次提交
-
-
由 Richard Levitte 提交于
consistent with the rest of the AEP functions
-
由 Richard Levitte 提交于
-
- 08 2月, 2002 4 次提交
-
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
CRYPTO_LOCK_RAND...
-
由 Richard Levitte 提交于
lets change our prefix to AEPHK_R_. Otherwise, we get very mysterious errors because we happen to redefine AEP_R_OK and AEP_R_GENERAL_ERROR.
-
由 Richard Levitte 提交于
that were never part of the engine framework. The aep and sureware implementations are taken directly from 0.9.6c [engine] and have been modified to fit the newer engine framework and to be possible to build shared libraries of. The aep implementation has gone through quite a bunch of tests and is cleaned up (there were some misunderstandings in it about how to use locks). The sureware hasn't been tested at all in this incarnation and is basically a quick hack to get it to compile properly.
-