Praising sodium_malloc as secure annoys me. Its memset is definitely not secure. It is just not skipped, but it is not meltdown secure, so prone to sidechannel

Praising sodium_malloc as secure annoys me. Its memset is definitely not secure. It is just not skipped, but it is not meltdown secure, so prone to sidechannel attacks. My fix was rejected, because a secure memset would be too slow (flushing the caches). So the headline should be fast crypto, in opposition to secure crypto.