This site is not geared for the hard-core Computer Security person who wishes to read papers on security or discuss Linux Security. It is geared for the person who wants to do one stop shopping for their Linux Security Bugs. The goal of this page is be a web site where one gets holes, exploits, patches, and fixes easily and quickly, without having to find out the hard way (READ: Break in) that there is a hole in a certain piece of software they use.
Also, the information here, is none of my own creating. It is many other persons work that I have collected and refined, and I will try to give them the much desired credit they need. Again, I will try to have pointers to where I have collected the information from.
2. Due to the number of Linux Holes and wide array of Linux distributions, I am unable to test every hole on every Linux Distributions. If it works for Slackware, then there is a really good chance it might work on all of the other Linux distributions.
3. I have received several holes where the only thing I have is the exploit and nothing else. So what I have to do is sit down and figure out what it does, where it does it and how it does it. Then track down other sources of information and piece together the warning. So if there is any problems with a hole posted here, let me know.
4. If a hole is old (2 Years +) then most likely it will not be here. I only deal with holes from the latest distributions back to Slackware 2.0. Anything after that, and you should really upgrade.
5. If you have not noticed already, I primary deal with Non-Red Hat Distributions holes. Red Hat has their own Security stuff, and thus you should deal with them for fixes and such.
6. Any program that is in the "Programs To Help Keep Your System Safe" I have compiled and installed on my personal machine, or some other Linux box. So I stand behind their use 110%!
7. This page is written in American Standard English with a Southern California flair, on a slight Texan accent. Those of you who learned english from the English (My European readers) might be thrown off by my use of english. If you have any questions, please feel free to write me and I will explain any wording the best I can.
2. California State University Chico or California State University Chico Engineering Computer Science and Technology Department is not responsible for the information on this page nor who uses it and how they use it. Again, the security of your system is your responsibility, not California State University Chico or California State University Chico Engineering Computer Science and Technology Department.