3 ms·
I think the more obvious way to keep private data unreadable is ensuring memory safety: write only the performance critical parts in memory unsafe languages lik
by legulere 11y ago
I think the more obvious way to keep private data unreadable is ensuring memory safety: write only the performance critical parts in memory unsafe languages like C and prove them memory safe.
- viraptor 11y agoYou realise that definition also applies to hardware keys, right? They're unreadable, private data via memory safety - there's only limited interface to operate on that data in valid ways. Proving code correct is far from obvious though. Apart from single instances like sel and python's sort, can you remember any verified software with proofs right now?
- legulere 11y agoMemory safety is only a subset of verification. In fact, most programming languages are memory safe (although I think there are no formal proofs, I haven't come across memory unsafety in a language that claims to be memory safe). seL4 is actually another verified software I know.
- viraptor 11y ago"Apart from single instances like sel and python's sort" ...
- lawnchair_larry 11y agoBut then it's actually impossible to erase them from memory!