Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
How did you determine this? Did you perform some sort of vulnerability scan, or are you going solely by the version numbers? If it's the latter, keep in mind that it's quite normal for distros to leave software version numbers intact when backporting security patches (the package version number is what gets bumped). Have you checked the relevant package's changelog to see if there is a record of the vulnerabilities you're referring to having been addressed?
We have a 3rd party doing a Qualys PCI scan. It's very frustrating, because it seems they are only going off version number, and i really, really do not like installing from src if I don't have to.
You should explain to them that what they are doing is extremely stupid.
If they force you to needlessly upgrade software you are more likely to introduce new security bugs. For production servers backporting the fixes (as is done in RHEL/CentOS, Debian etc.) is the way to go. If they (the 3rd party) don't understand this then I shudder to think what else they screw up.
By simply removing the Apache version in the header information, it was enough to trick Qualys into believing we're up to date, and or actually trying the vuln. Anyways - we're in the clear - thanks guys!