|
|
|
|
|
by kmeisthax
180 days ago
|
|
I have to wonder if we need, say, a special "secret data" type (or modifier) that has the semantics of both crypto/subtle and runtime/secret. That is to say, comparison operators are always constant-time, functions holding the data zero it out immediately, GC immediately zeroes and deallocs secret heap allocations, etc. I mean, if you're worried about ensuring data gets zeroed out, you probably also don't want to leak it via side channels, either. |
|