 Dr. Matthias St. Pierre
|
8529b15642
test/secmemtest: test secure memory only if it is implemented
|
6 years ago |
 Pauli
|
3b8e97ab61
Zero memory in CRYPTO_secure_malloc.
|
6 years ago |
 Kurt Roeckx
|
3cb7c5cfef
Use void in all function definitions that do not take any arguments
|
6 years ago |
 Andy Polyakov
|
f1c00b93e2
mem_sec.c: portability fixup.
|
6 years ago |
|
Andy Polyakov
|
014cc4b27a
mem_sec.c: portability fixup.
|
6 years ago |
|
Andy Polyakov
|
5839185cdd
mem_sec.c: relax POSIX requirement.
|
6 years ago |
 Benjamin Kaduk
|
63ab5ea13b
Revert the crypto "global lock" implementation
|
6 years ago |
 Bernd Edlinger
|
154d8c132f
Add a configure option to opt-out secure memory
|
6 years ago |
 Richard Levitte
|
48e5119a6b
Copyright update of more files that have changed this year
|
6 years ago |
|
Richard Levitte
|
e44c7d02dd
Only implement secure malloc if _POSIX_VERSION allows
|
6 years ago |
 Rich Salz
|
cbe2964821
Consistent formatting for sizeof(foo)
|
7 years ago |
|
Rich Salz
|
ed6b2c7938
Add CRYPTO_thread_glock_new
|
7 years ago |
|
Pauli
|
07016a8a31
Move e_os.h to be the very first include.
|
7 years ago |
|
Rich Salz
|
bef7a81530
Use "" not <> on e_os.h include
|
7 years ago |
|
Bernd Edlinger
|
4dae7cd3f0
Implement the CRYPTO_secure_clear_free function
|
7 years ago |
|
Rich Salz
|
624265c60e
Cleanup some copyright stuff
|
7 years ago |
 Todd Short
|
c8e89d58a5
Tweak sec_mem tests
|
7 years ago |
|
Todd Short
|
7031ddac94
Fix infinite loops in secure memory allocation.
|
7 years ago |
|
Todd Short
|
9dfc5b9687
Add support for MLOCK_ONFAULT to secure arena
|
7 years ago |
|
Rich Salz
|
332dc4fa5e
sh_malloc & sh_free prototype change to match POSIX
|
7 years ago |
|
Pauli
|
70e14ffbaf
Ensure minsize >= sizeof(SH_LIST)
|
7 years ago |
 Guido Vranken
|
7f07149d25
Prevent allocations of size 0 in sh_init, which are not possible with the default OPENSSL_zalloc, but are possible if the user has installed their own allocator using CRYPTO_set_mem_functions. If the 0-allocations succeeds, the secure heap code will later access (at least) the first byte of that space, which is technically an OOB access. This could lead to problems with some custom allocators that only return a valid pointer for subsequent free()-ing, and do not expect that the pointer is actually dereferenced.
|
7 years ago |
|
Rich Salz
|
4f22f40507
Copyright consolidation 06/10
|
8 years ago |
 Viktor Dukhovni
|
5c4328f04f
Fold threads.h into crypto.h making API public
|
8 years ago |
|
Todd Short
|
e8408681b3
Secure memory fixes
|
8 years ago |
 Matt Caswell
|
9471f7760d
Convert mem_dbg and mem_sec to the new Thread API
|
8 years ago |
 Rich Salz
|
a773b52a61
Remove unused parameters from internal functions
|
8 years ago |
 David Woodhouse
|
6a78ae2821
RT4313: Fix build for !IMPLEMENTED code path in CRYPTO_secure_free()
|
8 years ago |
|
Richard Levitte
|
05c7b1631b
Implement the use of heap manipulator implementions
|
8 years ago |
|
Richard Levitte
|
183733f882
Make sure to always include string.h so memset gets declared.
|
8 years ago |
