Index:
a.out(5)acct(5)
adduser.conf(5)
aliases(5)
amd.conf(5)
auth.conf(5)
big5(5)
bluetooth.hosts(5)
bluetooth.protocols(5)
bootparams(5)
bootptab(5)
config(5)
core(5)
crontab(5)
ctm(5)
cvs(5)
devd.conf(5)
devfs(5)
device.hints(5)
dhclient.conf(5)
dhclient.leases(5)
dhcp-eval(5)
dhcp-options(5)
dir(5)
dirent(5)
disktab(5)
editrc(5)
elf(5)
ethers(5)
euc(5)
eui64(5)
exports(5)
fbtab(5)
fdescfs(5)
finger.conf(5)
forward(5)
fs(5)
fstab(5)
ftpchroot(5)
gb18030(5)
gb2312(5)
gbk(5)
gettytab(5)
groff_font(5)
groff_out(5)
groff_tmac(5)
group(5)
hcsecd.conf(5)
hesiod.conf(5)
hosts(5)
hosts.equiv(5)
hosts.lpd(5)
hosts_access(5)
hosts_options(5)
inetd.conf(5)
info(5)
inode(5)
intro(5)
ipf(5)
ipnat(5)
ipnat.conf(5)
ipsend(5)
isdnd.acct(5)
isdnd.rates(5)
isdnd.rc(5)
kbdmap(5)
keycap(5)
keymap(5)
krb5.conf(5)
lastlog(5)
libarchive-formats(5)
libmap.conf(5)
link(5)
linprocfs(5)
loader.conf(5)
login.access(5)
login.conf(5)
mac.conf(5)
magic(5)
mailer.conf(5)
make.conf(5)
malloc.conf(5)
master.passwd(5)
moduli(5)
motd(5)
msdos(5)
msdosfs(5)
mskanji(5)
named.conf(5)
netconfig(5)
netgroup(5)
netid(5)
networks(5)
newsyslog.conf(5)
nologin(5)
nsmb.conf(5)
nsswitch.conf(5)
ntp.conf(5)
ntp.keys(5)
opieaccess(5)
opiekeys(5)
passwd(5)
pbm(5)
pccard.conf(5)
periodic.conf(5)
pf.conf(5)
pf.os(5)
phones(5)
printcap(5)
procfs(5)
protocols(5)
publickey(5)
pw.conf(5)
quota.group(5)
quota.user(5)
radius.conf(5)
rc.conf(5)
rcsfile(5)
remote(5)
resolv.conf(5)
resolver(5)
rhosts(5)
rndc.conf(5)
rpc(5)
rrenumd.conf(5)
rtadvd.conf(5)
services(5)
shells(5)
ssh_config(5)
sshd_config(5)
stab(5)
style.Makefile(5)
sysctl.conf(5)
syslog.conf(5)
tacplus.conf(5)
tar(5)
term(5)
termcap(5)
terminfo(5)
texinfo(5)
tmac(5)
ttys(5)
tzfile(5)
usbd.conf(5)
utf2(5)
utf8(5)
utmp(5)
uuencode(5)
uuencode.format(5)
vgrindefs(5)
wtmp(5)
tacplus.conf(5)
NAME
tacplus.conf -- TACACS+ client configuration file
SYNOPSIS
/etc/tacplus.conf
DESCRIPTION
tacplus.conf contains the information necessary to configure the TACACS+ client library. It is parsed by tac_config() (see libtacplus(3)). The file contains one or more lines of text, each describing a single TACACS+ server which is to be used by the library. Leading white space is ignored, as are empty lines and lines containing only comments. A TACACS+ server is described by two to four fields on a line. The fields are separated by white space. The `#' character at the beginning of a field begins a comment, which extends to the end of the line. A field may be enclosed in double quotes, in which case it may contain white space and/or begin with the `#' character. Within a quoted string, the double quote character can be represented by `\"', and the backslash can be represented by `\\'. No other escape sequences are supported. The first field specifies the server host, either as a fully qualified domain name or as a dotted-quad IP address. The host may optionally be followed by a `:' and a numeric port number, without intervening white space. If the port specification is omitted, it defaults to 49, the standard TACACS+ port. The second field contains the shared secret, which should be known only to the client and server hosts. It is an arbitrary string of characters, though it must be enclosed in double quotes if it contains white space or is empty. An empty secret disables the normal encryption mechanism, causing all data to cross the network in cleartext. The third field contains a decimal integer specifying the timeout in sec- onds for communicating with the server. The timeout applies separately to each connect, write, and read operation. If this field is omitted, it defaults to 3 seconds. The optional fourth field may contain the string `single-connection'. If this option is included, the library will attempt to negotiate with the server to keep the TCP connection open for multiple sessions. Some older TACACS+ servers become confused if this option is specified. Up to 10 TACACS+ servers may be specified. The servers are tried in order, until a valid response is received or the list is exhausted. The standard location for this file is /etc/tacplus.conf. An alternate pathname may be specified in the call to tac_config() (see libtacplus(3)). Since the file contains sensitive information in the form of the shared secrets, it should not be readable except by root.
FILES
/etc/tacplus.conf
EXAMPLES
# A simple entry using all the defaults: tacserver.domain.com OurLittleSecret
SEE ALSO
libtacplus(3)
AUTHORS
This documentation was written by John Polstra, and donated to the FreeBSD project by Juniper Networks, Inc. FreeBSD 5.4 July 29, 1998 FreeBSD 5.4
SPONSORED LINKS
Man(1) output converted with man2html , sed , awk