On Sun, Sep 12, 2010 at 1:51 PM, tedd <tedd.sperl...@gmail.com> wrote:
> At 1:18 PM -0400 9/12/10, Andy McKenzie wrote:
>>> A question, to clarify my fuzzy thinking about such things:
>>> Can a business have a server connected to the Internet but limit access
>>> just their employees? I don't mean a password protected scheme, but
>>> the server being totally closed to the outside world other than to their
>>> internal employees? Or is this something that can only be provided by a
>>> with no Internet connection?
>> Hey, one I can answer!
>> The short answer is "Yes". It can be done in a firewall: for
>> instance, take the following network setups.
>> 1) Internal machines on a single range (10.10.0.1-10.10.0-254),
>> gateway machine at 10.10.0.1, web server at 10.10.0.2.
>> In this situation, the gateway passes traffic web traffic from
>> outside to 10.10.0.2/80 (destination NATing, in linux's iptables), and
>> traffic from inside to 10.10.0.2/8880. There's no reasonable way for
>> outside traffic to reach the web server, but the web server can still
>> reach the outside world. If you don't want to have ANYONE outside the
>> private network reach the web server, you can eliminate the dnat rule
>> so port 80 traffic isn't forwarded. If the employees need access from
>> outside, a VPN would work best, as Ash suggested, but there are other
>> options. The catch is that you need to either use virtual hosts,
>> which brings one set of problems, or two pieces of web-server software
>> (two instances of apache, for instance), which brings a different set
>> of problems.
>> 2) All systems on publicly reachable addresses
>> (184.108.40.206-220.127.116.11, to pick at random). The web server is at
>> 18.104.22.168, there is no gateway. The firewall here needs to be on the
>> web server, since there is no gateway, and it only allows port 8880
>> traffic in if it's from the range 22.214.171.124/24. Again, if no
>> external access is necessary, it can be simplified somewhat.
>> In either instance, employees with permanent IP addresses at home can
>> be allowed in via the firewall.
> Many thanks -- now I need to figure what you said and how to implement it.
> Does this mean that my client will need a physically local server with
> fire-wall software protection or can this be done in conventional remote
> hosting environment with htaccess (or whatever) directives?
> I really need to understand the basics.
> Thanks for your help.
First off, I don't recommend trying to build a secure firewall
yourself if you don't know what you're doing, much like I wouldn't
recommend building your own web server. There are a lot of potential
pitfalls, and ways to make things look like they're secure when they
That said, here's my take.
It sounds from what you said like you have a client with the following setup:
- Machines in the office, probably on a private subnet with a single
public IP showing (this is Network Address Translation, or NAT).
- A remote server rented from a hosting company. Hopefully it's
running Linux/Apache, rather than Windows/anything, because it's
easier (for me, at least) if it's linux. I'll assume it's running
Linux and Apache, since most hosting companies do things that way, in
This is potentially the hardest setup, security-wise. You're
looking at all data having to travel over a network connection, which
means it's inherently insecure, and you may not have full access to
the server. If you've got access to either the firewall or the apache
config on the server, though, you can make it work. There are two
1) Firewall. You can use the firewall (iptables, in my assumed
scenario) to restrict who can reach the server. Find someone who
knows what they're doing to set this up, or you can lock yourself out
of the server really easily -- I've done it several times at work, and
it's always embarrassing.
2) Apache config. You can set a particular subdirectory of your
Apache install -- or the whole thing! -- to only be accessible to
people from certain domains or IPs. The way to do this is to use a
"Deny all" directive, followed by, say "Allow .myclient.com" or "Allow
126.96.36.199" if that's your gateway. See
http://articles.techrepublic.com.com/5100-22_11-5076696.html for some
basic information -- look at the section with the header "Restrict
access". This is easier, but I'm not sure whether it's as secure.
Best, of course, would be to do both. That way no one unauthorized
should be able to reach the server, but if they manage, it should
still lock them out.
Now: this all works the same for an internal server. The only
difference really is that you're in full physical control, and you can
drop the whole thing behind a gateway firewall as well as the internal
firewall. It is generally a good idea to let a server access the
internet, since that's the easiest way to download and install
security patches, but you can still restrict access the same way.
Either you put two network cards in the server, and use one to access
the internet and the other for the internal network, or you use one,
and use the firewall and Apache directives to control who has access.
Again, though, I don't advocate setting up a secure server yourself
if you don't know what you're doing: that's fine if it doesn't really
have to be secure and it's for yourself (that's a good way to learn,
actually), but you're running a big risk if you sell someone a secure
solution that turns out to not really be secure.
I hope this helps!
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php