3 ms·
It's not all bad news. "Transactional Memory" seems to have flopped for lock-free synchronization, but it is a nice way to keep writes from ever going out to R
by ncmncm 8y ago
It's not all bad news.
"Transactional Memory" seems to have flopped for lock-free synchronization, but it is a nice way to keep writes from ever going out to RAM or beyond. It reserves a bit of cache for temporary storage, and automatically wipes it if anything happens, like an interrupt -- even on a guest OS.
That is better than zeroing, and the toolchain won't fight you. But it might not be available everywhere you want it.
Also, it wasn't designed for crypto, so there are probably vulnerabilities to the host OS.
- monocasa 8y agoTransactional memory doesn't help you here. Everything will be cleared, including whatever you were trying to do with the secret.
- ncmncm 8y agoIt means you have to start over if it gets cleared. That adds latency spikes to processes that use it, which have to be planned for. Everything around security is hard. It gets easier if you don't care whether it really is secure, which is common.