Setting up the Gateway Services
This section describes how to setup each piece of the authentication gateway. The examples used are for a public network in the 10.0.1.0 subnet. eth0 is the interface on the box that is connected to the internal network. eth1 is the interface connected to the public network. The IP address used for this interface is 10.0.1.1. These settings can be changed to fit the network you are using. Red Hat 7.1 was used for the gateway box, so a lot of the examples are specific to Red Hat.
Netfilter Setup
To setup netfilter the kernel must be recompiled to include netfilter support. Please see the Kernel-HOWTO for more information on configuring and compiling your kernel.
This is what my kernel configuration looked like.
# |
Once netfilter has been configured, turn on IP forwarding by executing this command.
echo 1 > /proc/sys/net/ipv4/ip_forward |
To make sure ip forwarding is enabled when the machine restarts add the following line to /etc/sysctl.conf.
net.ipv4.ip_forward = 1 |
If NocatAuth is being used, you can skip to the NoCatAuth gateway setup section.
iptables needs to be installed. To install iptables either use a package from your distribution or install from source. Once the above options were compiled in the new kernel and iptables was installed, I set the following default firewall rules.
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE |
The above commands can also be put in an initscript to start up when the server restarts. To make sure the rules have been added issue the following commands:
iptables -v -t nat -L |
To save these rules I used Red Hat's init scripts.
/etc/init.d/iptables save |
Now the gateway box will be able to do network address translation (NAT), but it will drop all forwarding packets except those coming from within the public network and bound for the gateway.
Netfilter rules.
This section describes how to setup the software needed to dynamically insert and remove Netfilter rules on the gateway.
iptables Module
The PAM session module that inserts the firewall rules is needed to allow forwarding for the authenticated client. To set it up simply get the source and compile it by running the following commands.
gcc -fPIC -c pam_iptables.c |
You should now have two binaries called pam_iptables.so and pam_iptables.o. Copy pam_iptables.so to /lib/security/pam_iptables.so.
cp pam_iptables.so /lib/security/pam_iptables.so |
Now install the firewall script to /usr/local/auth-gw.
mkdir /usr/local/auth-gw |
The chosen authentication client for the gateway was ssh so we added the following line to /etc/pam.d/sshd.
session required /lib/security/pam_iptables.so |
Now, when a user logs in with ssh, the firewall rule will be added.
To test if the pam_iptables module is working perform the following steps:
Log into the box with ssh.
Check to see if the rule was added with the command iptables -L -v.
Log out of the box to make sure the rule is removed.
gateway
This section describes the process of setting up the NocatAuth gateway. To setup NocatAuth get the source and install with the following steps.
Make sure gpgv is installed. gpgv is a PGP signature verifier. It is part of gnupg and can be found at http://www.gnupg.org/download.html.
Unpack the NocatAuth tar file.
tar xvzf NocatAuth-x.xx.tar.gz |
If you do not want NoCatAuth to be in the directory /usr/local/nocat, edit the Makefile and change INST_PATH to the directory you would like NoCatAuth to reside.
Next build the gateway.
cd NoCatAuth-x.xx |
Edit the /usr/local/nocat.conf file. Please see the INSTALL documentation for details on what is required in the conf file. An example conf file looks like the following:
|
Now you should be able to start the gateway. If any problems occur, please see the INSTALL documentation in the unpacked NoCatAuth directory. The following command will start the gateway:
/usr/local/nocat/bin/gateway |
Server Setup
I installed DHCP using the following dhcpd.conf file.
subnet 10.0.1.0 netmask 255.255.255.0 { |
The server was then run using eth1 , the interface to the public net.
/usr/sbin/dhcpd eth1 |
Authentication Method Setup
Authentication with PAM and a NoCatAuth authentication service is described. Both examples are done with LDAP. Other means of authentication besides LDAP can be used. Please read the documentation for PAM and NoCatAuth to find the steps to use another authentication source.
LDAP
As indicated in previous sections, I've set this gateway up to use LDAP for authenticating. However, you can use any means that PAM allows for authentication. See Section 2.4 for more information.
In order to get PAM LDAP to authenticate, I installed OpenLDAP and configured it with the following in /etc/ldap.conf.
# Your LDAP server. Must be resolvable without using LDAP. |
The following files were used to configure PAM to do the LDAP authentication. These files were generated by Red Hat's configuration utility.
- /etc/pam.d/system-auth was created and looked like this.
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth required /lib/security/pam_env.so
auth sufficient /lib/security/pam_unix.so likeauth nullok
auth sufficient /lib/security/pam_ldap.so use_first_pass
auth required /lib/security/pam_deny.so
account required /lib/security/pam_unix.so
account [default=ok user_unknown=ignore service_err=ignore system_err=ignore] /lib/security/pam_ldap.so
password required /lib/security/pam_cracklib.so retry=3
password sufficient /lib/security/pam_unix.so nullok use_authtok
password sufficient /lib/security/pam_ldap.so use_authtok
password required /lib/security/pam_deny.so
session required /lib/security/pam_limits.so
session required /lib/security/pam_unix.so
session optional /lib/security/pam_ldap.so
- Then the following /etc/pam.d/sshd file was created.
#%PAM-1.0
auth required /lib/security/pam_stack.so service=system-auth
auth required /lib/security/pam_nologin.so
account required /lib/security/pam_stack.so service=system-auth
password required /lib/security/pam_stack.so service=system-auth
session required /lib/security/pam_stack.so service=system-auth
#this line is added for firewall rule insertion upon login
session required /lib/security/pam_iptables.so debug
session optional /lib/security/pam_console.so
Service
It is recommended to install the NoCatAuth Service on another server besides the gateway. A seperate server was used in my examples. In order to setup a NoCatAuth Service, you will need the following software:
An SSL enabled webserver, preferably with a registered SSL cert. I used Apache + mod_ssl.
Perl 5 (5.6 or better recommended)
Net::LDAP, Digest::MD5, DBI, and DBD::MySQL perl modules (get them from CPAN) The module you need depends on what authentication source you are going to use. In my example Net::LDAP is used as the authentication means.
Gnu Privacy Guard (gnupg 1.0.6 or better), available at http://www.gnupg.org/download.html
To install unpack the tar file.
$ tar zvxf NoCatAuth-x.xx.tar.gz |
If you would like to change the path that NoCatAuth resides , edit the Makefile and change INST_PATH to the desired directory.
Next run the command: make authserv This installs everything in /usr/local/nocat or what you changed INST_PATH to.
Then run make pgpkey The defaults should be fine for most purposes. IMPORTANT: do NOT enter a passphrase! Otherwise, you will get strange messages when the auth service attempts to encrypt messages, and tries to read your passphrase from a non-existent tty
Edit /usr/local/nocat/nocat.conf to fit your situation. Here is an example:
###### authserv.conf -- NoCatAuth Authentication Service Configuration. |
Make sure /usr/local/nocat/pgp is owned by the web server user. (ie..nobody or www-data)
Add etc/authserv.conf to your apache httpd.conf file.
Include /usr/local/nocat/etc/authserv.conf |
Copy your /usr/local/nocat/trustedkeys.pgp to the gateway. Restart apache and try it out. Please see the NoCatAuth documentation for more information. It can be found in docs/ in the unpacked NoCatAuth directory.
Komentar