4 ms·
So, we just finished extricating this from our codebase. My main issues: 1) The underlying primitives weren't really meant for this use case. They don't guar
by monocasa 7y ago
So, we just finished extricating this from our codebase.
My main issues:
1) The underlying primitives weren't really meant for this use case. They don't guarantee that a copy is flushed to disk, just that the canonical copy remains in RAM.
2) By creating pointers that are ostensibly supposed to be used, that aren't known to the GC, you're opening yourself up to a whole lot of use after free vulnerabilities, and just generally breaking the memory safety of the runtime. The other main area where you deal with raw non-GCed pointers like this is CGo, where you generally marshal into the GCed world as fast as you can for the reasons above.
3) What's the actual threat model here? Is stopping people from reading a core dump worth breaking the memory safety of the runtime?
- techslave 7y ago> 3) What's the actual threat model here? Is stopping people from reading a core dump worth breaking the memory safety of the runtime? well yeah. that’s the point. if you don’t want to write an entire application in C to prevent this. if for your application it’s not worth it, you live with it.
- monocasa 7y agoI can't quite follow all of the indefinite pronouns. Can you restate?