Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
| 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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
03-14-2008, 06:38 PM
|
#1
|
|
Member
Registered: Mar 2008
Posts: 52
Rep:
|
Basic security measures to take connecting a Linux server to the Internet.
I am configuring a CentOS system to act as a PDC for a predominantly Windows-based network (all clients are Windows XP).
This server will be directly connected to the Internet through a small Linksys router, and will have a static IP associated with it. It will provide web services to the public. It must also make SSH available for administration purposes. Any other services will be strictly internal.
What sort of security measures should I implement on this server to keep it secure from outside attack, yet still be administerable from the Internet?
I realize this is a broad question, so a range of answers are possible. I will award points to the most helpful information.
Thanks!
|
|
|
|
03-14-2008, 08:13 PM
|
#2
|
|
Guru
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,817
|
Well, limit what ports are open to the Internet from the router, first off. If you just need SSH and WWW, then only open those two ports.
To secure SSH, disable root logins and use strong passwords. You might want to play around with the values for simulations logins, failed authentication attempts, etc to prevent brute-forcing passwords; but really, SSH is very secure and the chances of brute-forcing a password is very low even with the default settings due to the way it handles authentication.
As for securing Apache, that is a bit bigger of an issue. It depends on what modules you need, how the site is going to operate, etc, etc. I would start reading up on Apache security before you go live with the site, you want to know what specific security adjustments apply to you and your site before it is publicly available.
|
|
|
|
03-15-2008, 09:42 PM
|
#3
|
|
Moderator
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 22,903
|
I'd like to discourage members to respond to these posts.
This is the product of a SPAM bot.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 03:40 AM.
|
|
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
|
|