Browse Source

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@
OPENBSD_5_6
beck 10 years ago
parent
commit
8e9fe71de4
1 changed files with 2 additions and 2 deletions
  1. +2
    -2
      src/lib/libcrypto/crypto/Makefile

+ 2
- 2
src/lib/libcrypto/crypto/Makefile View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.13 2014/04/15 22:44:15 tedu Exp $
# $OpenBSD: Makefile,v 1.14 2014/04/16 03:24:53 beck Exp $
LIB= crypto
@ -42,7 +42,7 @@ CFLAGS+= -I${LCRYPTO_SRC}
CFLAGS+= -I${LCRYPTO_SRC}/modes -I${LCRYPTO_SRC}/asn1 -I${LCRYPTO_SRC}/evp
# crypto/
SRCS+= cryptlib.c mem.c mem_dbg.c cversion.c ex_data.c cpt_err.c
SRCS+= cryptlib.c malloc-wrapper.c mem_dbg.c cversion.c ex_data.c cpt_err.c
SRCS+= uid.c o_time.c o_str.c o_fips.c o_init.c
# aes/


Loading…
Cancel
Save