Is it possible to protect an old, unpached apache server?
Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Is it possible to protect an old, unpached apache server?
I badly need a place where I could make just one single jpeg freely downloadable to the internet.
Presently we have no http servers aaccessible from the internet, but one that is only accessible from within our LAN. It is an unpatched, 4-years old apache installation on a FreeBSD 4.4 machine. There is no GUI on that machine, and it is in a non-unix network environment.
I wonder if I could put the jpeg on that http server and make it accessible to the internet?
(I have got no maintenance time for four years, so patching/upgrading the server is out of question, though our whole intranet relies on that FreeBSD machine)
I wonder if it is possible to start a new (virtual) http server on that machine that should have no access to any files on that machine except for that jpeg. It should listen on a non-http port, and that port could be forwarded to a non-http port of our firewall.
Hiding the server behind e.g. stunnel is, however, not possible, as the jpeg should be accessible without authentication.
How to start a virtual http server that only has access to one single file (though there is an other http server on the same machine that should have access and serve documents for the intranet), it does not serve e.g. php pages (though php pages should be accessible from within the LAN), it should listen on a different port.
I wonder if it would be too risky to put an unpatched apache on the internet even if those conditions can be fulfilled?
Re: Is it possible to protect an old, unpached apache server?
Quote:
Originally posted by J_Szucs (I have got no maintenance time for four years, so patching/upgrading the server is out of question, though our whole intranet relies on that FreeBSD machine)
How can you have no time to do maintenance on a server in 4 years?? Sounds like it can't be that critical of a server if patching isn't important...
At any rate, you should just make time to upgrade Apache. You can compile Apache2 from source in <15 minutes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.