# MSNT Auth v2.0.3-squid.1
Squid web proxy NT authentication module
Modified by the Squid HTTP Proxy team
Wed Jun 26 21:16:32 CEST 2002
Original release by Antonino Iannella, Stellar-X Pty Ltd

## Contents

- Introduction
- Installation
- Issues when compiling
- Configuration file
- Denying users
- Allowing users
- Squid.conf changes
- Testing
- Contact details
- Unknown username issue
- Revision history

## Introduction

This is an authentication module for the Squid proxy server to use an NT domain server.

It originates from the Samba and SMB packages by Andrew Tridgell and Richard Sharpe. It is sourced from the Pike authentication module by William Welliver (hwellive@intersil.com), and the SMB 1.0.1 libraries. Releases up to version 2.0.3 were created by Antonino Iannella (antonino@rager.com.au, http://stellarx.tripod.com). The module is now distributed with Squid, and is maintained by the Squid proxy team as an Open Source effort. Msntauth is released under the GNU General Public License.

Usage is simple. It accepts a username and password on standard input. It will return OK if the username/password is valid for the domain, or ERR if there was some problem. Check syslog messages for reported problems.

Msntauth works in environments with NT domain controllers on Windows (TM) NT 4, 2000, and Samba.

## Installation

Msntauth will be compiled when you compile Squid, using their autoconf system. Refer to Squid documentation for details. If the build is suitable, you can skip this section.

Alternatively, a supplementary makefile is also provided for manual compiling. Review Makefile.MSNT, and modify it based on the target platform or site requirements.

Make any necessary changes to the source code.

Copy Makefile.MSNT to Makefile. Type 'make', then 'make install', then 'make clean'.

To avoid using the makefile, it may compile with gcc -O2 -s -o msntauth *.c

'Make install' will put 'msntauth' into /usr/local/squid/bin.

## Issues when compiling

The Makefile uses your C compiler (usually GCC), assuming it's in your PATH. Msntauth is known to compile properly on Linux, FreeBSD, and Solaris.

When compiling under Solaris, link to the NSL and socket libraries. In the Makefile, enable the alternative CFLAGS line for Solaris. Ensure /usr/ccs/bin is in your PATH. In Smbencrypt.c, '#include ' only gets included when compiled with Solaris.

For Digital Unix/Tru64, review the INSTALL line in the makefile. The install-bsd command is used to place files in their target location.

## Configuration file

Msntauth uses a configuration file, usually /usr/local/squid/etc/msntauth.conf. To change this, edit the following line in confload.c -

      #define CONFIGFILE   "/usr/local/squid/etc/msntauth.conf"

An example configuration file is provided -

    # Sample MSNT authenticator configuration file
    # Antonino Iannella, Stellar-X Pty Ltd
    # Tue Aug 26 17:26:59 GMT+9 2003

    # NT domain hosts. Best to put the hostnames in /etc/hosts.
    server myPDC           myBDC          myNTdomain
    server otherPDC        otherBDC       otherdomain

    # Denied and allowed users. Comment these if not needed.
    denyusers       /usr/local/squid/etc/denyusers
    allowusers      /usr/local/squid/etc/allowusers

All comments start with '#'.

NT servers are used to query user accounts. The 'server' lines are used for this, with the PDC, BDC, and NT domain as parameters. Up to 5 servers/domains can be queried. If this is not enough, modify the MAXSERVERS define in confload.c. At least one server must be specified, or msntauth will not start. Server names must be resolvable by the system. If not, msntauth reports an error. If you can't ping it, you might have a host resolution problem.

The name you specify is used in the NetBIOS protocol when communicating with the target server. The name must be resolvable by the local system, and it must be a name that the target server uses. You cannot simply invent a hostname. You cannot use it IP address.

When a user provides a username/password, each of these servers will be queried to authenticate the username. It stops after a user has been successfully authenticated, so it makes sense to specify the most commonly queried server first. Make sure the servers can be reached and are active, or else msntauth will report failures.

The 'denyusers' and 'allowusers' lines give the absolute path to files of user accounts. They can be used to deny or allow access to the proxy. Remove these directives if you do not need these features.

## Denying users

Users who are not allowed to access the web proxy can be added to the denied user list. This list is read around every minute, or when the msntauth process receives a SIGHUP signal.

The denied user file is set using the 'denyusers' directive in msntauth.conf. The denied user file contains a list of usernames, one per line. If the file does not exist, no users are denied. The file must be readable by the web proxy user.

Msntauth will send syslog messages if a user was denied, at LOG_USER facility. Check your syslog messages for clues.

## Allowing users

Similar to denying users, you can allow users to access the proxy by username. This is useful if only a number of people are allowed to use a proxy.

The allowed user file is set using the 'allowusers' directive in msntauth.conf. If the file does not exist or if empty, all users are allowed.

You could make use of the SHOWMBRS tool in Microsoft Technet. This gives you a list of users which are in a particular NT Domain Group. This list can be made into the allowed users file using sed or awk.

Some other rules -

1. The operation of the denied user file is independent of the allowed user file. The former file is checked first.
2. You can use none, one, or both files.
3. If a username appears in the denied user file, they will be denied, even if they are in the allowed user file.
4. If a username is not in either file, they will be denied, because they have not been allowed.
5. If the allowed user file is in use and is empty, all users will be allowed.

## Squid.conf changes

Refer to Squid documentation for the required changes to squid.conf. You will need to set the following lines to enable authentication for your access list -

      acl yourACL proxy_auth REQUIRED
      http_access allow password
      http_access allow yourACL
      http_access deny all

You will also need to review the following directives. The number of msntauth children spawned is set with authenticate_children. The number of children needed is site-dependent, so some experimentation may be required to find the best number. There should be no visible delay in performance with Squid once msntauth is in use. As an example, a firm with 1500 users and a T1 internet connection required a value of 30.

      proxy_auth_realm enterprise web gateway
      authenticate_program /usr/local/squid/bin/msntauth
      authenticate_ttl 5
      authenticate_children 20

## Testing

I strongly urge that Msntauth is tested prior to being used in a production environment. It may behave differently on different platforms. To test it, run it from the command line. Enter username and password pairs separated by a space.

It should behave in the following way -

     - Press ENTER to get an OK or ERR message.
     - Make sure pressing CTRL-D behaves the same as a carriage return.
     - Make sure pressing CTRL-C aborts the program.
     - Test that entering no details does not result in an OK or ERR message.
     - Test that entering an invalid username and password results in
       an ERR message. Note that if NT guest user access is allowed on
       the PDC, an OK message may be returned instead of ERR.
     - Test that entering an valid username and password results in an OK message.
       Try usernames which are and aren't in the denied/allowed user files,
       if they're in use.
     - Test that entering a guest username and password returns the correct response.

If the above didn't work as expected, you may need to modify the main() function in msntauth.c. Inform the Squid maintainers of any problems.

Usernames cannot have whitespace in them, but passwords can.

As of version 2.0.3, the msntauth version can be found in the executable. Type this to retrieve it -

      strings msntauth | grep -i msntauth

## Support details

Refer to the Squid website at http://www.squid-cache.org. Submit problems or fixes using their Bugzilla facility.

## Unknown username issue

For an unknown username, Msntauth returns OK. This is because the PDC returns guest access for unknown users, even if guest access is disabled. This problem was reported by Mr Vadim Popov (vap@iilsr.minsk.by).

The tested environment consisted of PDC on Windows NT 4, SP 6. Squid 2.3 and Msntauth was tested on SuSe, RedHat, and Debian Linux. A fix was provided in case you have this problem. Apply the provided patch before compiling, using

      patch smblib.c < smblib.c.patch

## Revision history

The following sequence of changes have been made to improve msntauth.

- Added many patches from Duane Wessels to stop compilation errors
- Improved the main() function yet again
- Created a more informative Makefile
- Added an 'allowed users' feature to complement the 'denied users' feature
- Stopped the use of alarm() which was causing problems under Solaris
- Added more syslog messages for authentication problems
- Added the use of a configuration file, instead of hard-coding NT server details
- Allowed for querying multiple NT servers and domains (this was a hot issue)
- Changed README into an HTML document to improve readability
- Removed denied/allowed username substring search limitation
- Fixed a bug which occurred when reading denied/allowed usernames
- Allows whitespace in passwords
- To check user list changes, doesn't use an alarm every minute.
- Fixed a sigaction compilation error, causing problems on FreeBSD and HPUX
- Removed a problem of finding a valid username as a substring in the denied user list.
- Support email address change from antonino@usa.net to antonino@rager.com.au.
- Msntauth was successfully tested on Tru64.
- PDC and BDC hostnames are now checked if they are resolvable.
- Smbencrypt.c does not have to be checked for Solaris systems any more.
- Imbedded version information in the executable.
- Version 2.0.3 and later now supported by the Squid team.

A future improvement may be to cache accepted usernames and passwords, to reduce network authentication traffic, and improve the Squid response time.