3 ms·
But now I have frozen an old language runtime and a bunch of old libraries into my environment, all of which are not just security hazards but interoperability
by saurik 1y ago
But now I have frozen an old language runtime and a bunch of old libraries into my environment, all of which are not just security hazards but interoperability landmines (a common one being lack of support for a new TLS standard).
- esseph 1y agoWrite a wrapper, don't expose the container. These are different problems from the distribution/bundling piece, they won't be solved the same way.
- saurik 1y agoI don't see how that solves either problem. If the thing in the container makes a web request out, that code both might become obsolete and offers an attack surface to get back in, and wrapping the outside of it doesn't change anything.
- ndriscoll 1y agoAs far as TLS is concerned it does: if you are running a server, run it through a TLS terminating reverse proxy. If you are running a client, run it through a TLS terminating forward proxy. As long as your application logic isn't exposed to a security issue, you're fine.