7 ms·

https://github.com/jedisct1/libsodium/blob/be5e5a53b35961e32f21355bd92df7ef0c69d7d5/src/libsodium/sodium/utils.c https://github.com/jedisct1/libsodium/blob/be5e

by dimitri1995 9y ago

https://github.com/jedisct1/libsodium/blob/be5e5a53b35961e32f21355bd92df7ef0c69d7d5/src/libsodium/sodium/utils.c https://github.com/jedisct1/libsodium/blob/be5e5a53b35961e32... They either do SecureZeroMemory for windows, memset or bzero for linux and in worst cases they manually wipe the array which is what memguard does, so, how is sodium_memzero any better in this case?

stouset 9y ago
It's not specifically about `sodium_memzero`, it's about managing the memory outside of the scope of go's garbage collector which can and will copy and move memory around as it sees fit. https://news.ycombinator.com/item?id=14174500 https://news.ycombinator.com/item?id=14174500