2 ms·
I think the dream is you could have one SSL process that others communicated with. Message passing at large.
by taeric 8y ago
I think the dream is you could have one SSL process that others communicated with. Message passing at large.
- otterley 8y agoIt's not without cost, though. Moving messages around causes CPU data cache pressure and CPU cycles you wouldn't otherwise have spent if you merely referenced shared memory that's mapped into your process.
- taeric 8y agoRight. I didn't mean that to be why it is correct. Just giving some comment to what was actually suggested. Static linking is not the only alternative to dynamic linking.
- joejev 8y agoSo, like some sort of shared library that my programs dynamically communicate with? How is this functionally different from a shared object?
- AnIdiotOnTheNet 8y agoIt isn't really. The actual big problem with shared libraries is that developers cannot be trusted not to change their interfaces or behavior and break things. That's true regardless of what mechanism you use to share code.
- a1369209993 8y ago> How is this functionally different from a shared object? Because it's a separate process, so when it crashes your application can put up a "SSL failed, reconnecting" message and carry on. Also when your application has read-something-somewhere security vulnerability, it can't compromise your SSL keys. Nitpick: it's not one process, but one executable; you can have multiple SSL daemons using the same (read-only) binary, so a attack on one only gets one set of keys. (The same attack will probably work on every instance of the same version of SSLd, but shared objects don't fix that.)