mbedtls_zeroize -> mbedtls_platform_zeroize in docs

This commit is contained in:
Andres Amaya Garcia 2018-04-24 08:33:31 -05:00
parent d0ef468d39
commit 708c5cb6ab
2 changed files with 5 additions and 5 deletions

View file

@ -909,7 +909,7 @@ rm -rf "$OUT_OF_SOURCE_DIR"
for optimization_flag in -O2 -O3 -Ofast -Os; do for optimization_flag in -O2 -O3 -Ofast -Os; do
for compiler in clang gcc; do for compiler in clang gcc; do
msg "test: $compiler $optimization_flag, mbedtls_zeroize()" msg "test: $compiler $optimization_flag, mbedtls_platform_zeroize()"
cleanup cleanup
CC="$compiler" DEBUG=1 CFLAGS="$optimization_flag" make programs CC="$compiler" DEBUG=1 CFLAGS="$optimization_flag" make programs
gdb -x tests/scripts/test_zeroize.gdb -nw -batch -nx gdb -x tests/scripts/test_zeroize.gdb -nw -batch -nx

View file

@ -25,10 +25,10 @@
# intelligent compiler could determine that this function clears a block of # intelligent compiler could determine that this function clears a block of
# memory that is not accessed later in the program, so removing the call to # memory that is not accessed later in the program, so removing the call to
# mbedtls_platform_zeroize() does not have an observable behavior. However, # mbedtls_platform_zeroize() does not have an observable behavior. However,
# inserting a test after a call to mbedtls_zeroize() to check whether the block # inserting a test after a call to mbedtls_platform_zeroize() to check whether
# of memory was correctly zeroed would force the compiler to not eliminate the # the block of memory was correctly zeroed would force the compiler to not
# mbedtls_platform_zeroize() call. If this does not occur, then the compiler # eliminate the mbedtls_platform_zeroize() call. If this does not occur, then
# potentially has a bug. # the compiler potentially has a bug.
# #
# Note: This test requires that the test program is compiled with -g3. # Note: This test requires that the test program is compiled with -g3.
# #