Linux - Security This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
09-27-2005, 10:21 AM
|
#1
|
Member
Registered: Apr 2005
Location: Milton Keynes
Distribution: ubuntu 12.10
Posts: 90
Rep:
|
securing php, apache and mysql
hello,
i would like to find quality documentation about securing php, mysql and apache... i've google it and found tons of info but i would like some experts advice of where is the GOOD documentation
|
|
|
09-28-2005, 01:57 AM
|
#2
|
Senior Member
Registered: Jan 2003
Location: Devon, UK
Distribution: Debian Etc/kernel 2.6.18-4K7
Posts: 2,380
Rep:
|
The key things that need to be addressed IMHO are:
1. Good iptables firewall.
2. Minimise the number of ports that are open. If you you don't need to ssh into the box from the net then close port 22 via the firewall as this is the port that is most commonly probed. If you need acccess only open it to the world via the firewall when you need to.
3. Probably the most important - have strong passwords.
4. Keep your software updated regularly.
Last edited by TigerOC; 09-28-2005 at 01:58 AM.
|
|
|
10-01-2005, 05:05 AM
|
#3
|
Senior Member
Registered: Dec 2003
Location: Brasil
Distribution: Arch
Posts: 1,037
Rep:
|
hi there,
Quote:
Originally posted by TigerOC
3. Probably the most important - have strong passwords.
|
agreed. considering the volume of "brute force" attacks nowadays this is the key.
on a side note, i suggest this tips for apache.
regards,
slackie1000
|
|
|
10-06-2005, 03:26 PM
|
#4
|
Member
Registered: Apr 2005
Location: Milton Keynes
Distribution: ubuntu 12.10
Posts: 90
Original Poster
Rep:
|
thanks for the tips... really appreciate them..... 
|
|
|
10-07-2005, 05:30 AM
|
#5
|
Member
Registered: Mar 2004
Distribution: Slackware current, DSL 0.9.2
Posts: 133
Rep:
|
mod_security is good. Also try some of the different kernel patches out there.
|
|
|
10-18-2005, 11:08 AM
|
#6
|
Member
Registered: Jan 2004
Location: Austin, TEXAS
Distribution: CentOS 6.5
Posts: 211
Rep:
|
Quote:
Originally posted by TigerOC
4. Keep your software updated regularly.
|
Of all these recommendations, I think #4 needs to be #1.
More websites get comprimised due to vulnerabilities in web applications than via brute-forced passwords. Usually, a vulnerability in some secondary piece of software is then used to elevate priveleges for the intruder.
di11rod
|
|
|
All times are GMT -5. The time now is 01:19 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|