2 ms·
I can't begin to see how it could possibly be secure to run different threads (read: shared memory) as your containerised primitive. That's just ridiculous. Sur
by cyphar 11y ago
I can't begin to see how it could possibly be secure to run different threads (read: shared memory) as your containerised primitive. That's just ridiculous. Sure, you might get some performance. But a bug in the version of Apache you're sharing between containers (which, in true shared hosting fashion, has taken security out of your hands) is going to break every container on the box (as well as whatever namespace the "master" Apache process is in).
And I'm not sure this model would work well with pool-based concurrency models (like with nginx, where work is given to workers, workers aren't spawned for each request).
However, it would be cool if this was just merged upstream, so that Apache could take advantage of the resource limiting. I'm not sure that it's a good general solution for shared hosts though (then again, you never trust shared hosts after you pop your first shell).
- iseletsk 11y agoWe would be happy to merge it upstream, but at this moment merging upstream requires much more work that we can dedicate to it.