Makefile revision 7014882c6a3672fd0e5d60200af8643ae53c5928
0N/A# Copyright 2009 Sun Microsystems, Inc. All rights reserved. 0N/A# Use is subject to license terms. 0N/A# Copyright 2011 Nexenta Systems, Inc. All rights reserved. 0N/A# Various components must export interfaces, but also contain name-space 0N/A# clashes with system libraries. 0N/A# The rest of this file contains definitions more-or-less directly from the 0N/A# original Makefile of the tcp_wrappers distribution. 0N/A############################## 0N/A# System parameters appropriate for Solaris 9 0N/A############################## 0N/A# Start of the optional stuff. 0N/A########################################### 0N/A# Optional: Turning on language extensions 0N/A# Instead of the default access control language that is documented in 0N/A# the hosts_access.5 document, the wrappers can be configured to 0N/A# implement an extensible language documented in the hosts_options.5 0N/A# document. This language is implemented by the "options.c" source 0N/A# module, which also gives hints on how to add your own extensions. 0N/A# Uncomment the next definition to turn on the language extensions 0N/A# (examples: allow, deny, banners, twist and spawn). 0N/A################################################################ 0N/A# Optional: Changing the default disposition of logfile records 0N/A# By default, logfile entries are written to the same file as used for 0N/A# path names of logfiles. The tutorial section in the README file 0N/A# gives a brief introduction to the syslog daemon. 0N/A# Change the FACILITY definition below if you disagree with the default 0N/A# disposition. Some syslog versions (including Ultrix 4.x) do not provide 0N/A# If nothing shows up on your system, it may be that the syslog records 0N/A# are sent to a dedicated loghost. It may also be that no syslog daemon 0N/A# is running at all. The README file gives pointers to surrogate syslog 0N/A# implementations for systems that have no syslog library routines or 0N/A# there must be TABs between fields. 0N/A# The syslog priority at which successful connections are logged. 0N/A###################################################### 0N/A# Optional: Changing the default file protection mask 0N/A# On many systems, network daemons and other system processes are started 0N/A# with a zero umask value, so that world-writable files may be produced. 0N/A# It is a good idea to edit your /etc/rc* files so that they begin with 0N/A# an explicit umask setting. On our site we use `umask 022' because it 0N/A# does not break anything yet gives adequate protection against tampering. 0N/A# The following macro specifies the default umask for processes run under 0N/A# control of the daemon wrappers. Comment it out only if you are certain 0N/A# that inetd and its children are started with a safe umask value. 0N/A####################################### 0N/A# Optional: Turning off access control 0N/A# By default, host access control is enabled. To disable host access 0N/A# control, comment out the following definition. Host access control 0N/A# can also be turned off at runtime by providing no or empty access 0N/A#################################################### 0N/A# By default, the software tries to protect against hosts that claim to 0N/A# have someone elses host name. This is relevant for network services 0N/A# whose authentication depends on host names, such as rsh and rlogin. 0N/A# With paranoid mode on, connections will be rejected when the host name 0N/A# does not match the host address. Connections will also be rejected when 0N/A# the host name is available but cannot be verified. 0N/A# Comment out the following definition if you want more control over such 0N/A# requests. When paranoid mode is off and a host name double check fails, 0N/A# the client can be matched with the PARANOID access control pattern. 0N/A# Paranoid mode implies hostname lookup. In order to disable hostname 0N/A# lookups altogether, see the next section. 0N/A# The default username lookup timeout is 10 seconds. This may not be long 0N/A# enough for slow hosts or networks, but is enough to irritate PC users. 0N/A######################################################## 0N/A# Optional: Changing the access control table pathnames 0N/A# The HOSTS_ALLOW and HOSTS_DENY macros define where the programs will 0N/A# look for access control information. Watch out for the quotes and 0N/A# backslashes when you make changes. 0N/A############################################# 0N/A# Optional: Turning on host ADDRESS checking 0N/A# Optionally, the software tries to protect against hosts that pretend to 0N/A# have someone elses host address. This is relevant for network services 0N/A# whose authentication depends on host names, such as rsh and rlogin, 0N/A# because the network address is used to look up the remote host name. 0N/A# The protection is to refuse TCP connections with IP source routing 0N/A# This feature cannot be used with SunOS 4.x because of a kernel bug in 0N/A# the implementation of the getsockopt() system call. Kernel panics have 0N/A# been observed for SunOS 4.1.[1-3]. Symptoms are "BAD TRAP" and "Data 0N/A# fault" while executing the tcp_ctloutput() kernel function. 0N/A# Reportedly, Sun patch 100804-03 or 101790 fixes this for SunOS 4.1.x. 0N/A# Uncomment the following macro definition if your getsockopt() is OK. 0N/A# -DKILL_IP_OPTIONS is not needed on modern UNIX systems that can stop 0N/A# source-routed traffic in the kernel. Examples: 4.4BSD derivatives, 0N/A# Solaris 2.x, and Linux. See your system documentation for details. 0N/A# KILL_OPT= -DKILL_IP_OPTIONS 0N/A## End configuration options 0N/A############################