Your operating system memory allocation functions are your friend. If they
authorbeck <beck@openbsd.org>
Wed, 16 Apr 2014 03:24:53 +0000 (03:24 +0000)
committerbeck <beck@openbsd.org>
Wed, 16 Apr 2014 03:24:53 +0000 (03:24 +0000)
commit75a7dac09710d4c70856e2406c0fc55d9c25ec3b
treebe16af47427296730a08f86663eb7603da626fba
parentce96de6b2a85274042f4be5a19a5ea6b28573097
Your operating system memory allocation functions are your friend. If they
are not please fix your operating system. Replace mem.c with an API-compatible
wrapper that just calls the system functions and does not allow a one word
modification of a variable in a running shared library to turn on memory
debug functions that expose things that should not be seen.
ok tedu@
lib/libcrypto/crypto/Makefile
lib/libcrypto/malloc-wrapper.c [new file with mode: 0644]
lib/libcrypto/mem.c [deleted file]
lib/libssl/src/crypto/malloc-wrapper.c [new file with mode: 0644]
lib/libssl/src/crypto/mem.c [deleted file]