9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I want to configure and run sshd server on my unix box. I already have that installed.
# yum -y install openssh-server openssh-clients
Loaded plugins: fastestmirror, presto, refresh-packagekit
Loading mirror speeds from cached hostfile
* base: centos.mirror.constant.com
* epel:... (1 Reply)
Discussion started by: nitalchandel
1 Replies
2. IP Networking
I have customer who controls access to the internet via TACACS server, basically a PIX firewall uses authentication from the TACACS to say if traffic is allowed to pass out of the gateway. I can't find anything on how to configure a linux client of TACACS authentication only how to set up a linux... (1 Reply)
Discussion started by: metallica1973
1 Replies
3. Cybersecurity
Can someone please posts the steps needed to configure a UNIX server to authenticate with a TACACS+ server or point me in the right direction been googling for 2 days now. Thanks (1 Reply)
Discussion started by: supadee718
1 Replies
4. UNIX for Advanced & Expert Users
Can someone please posts the steps needed to configure a UNIX server to authenticate with a TACACS+ server or point me in the right direction been googling for 2 days now. Thanks (0 Replies)
Discussion started by: supadee718
0 Replies
5. UNIX for Dummies Questions & Answers
Seek help configuring Sendmail 8.14.4 Unix server.
Not sure if this is the correct place to post or the Unix/Linux Forums job board. Seeking help configuring sendmail 8.14.4 on my Unix server. It appears I have an open relay. I was advised I need to modify a etc/mail/dir , a command line entry... (0 Replies)
Discussion started by: raecampus
0 Replies
6. Shell Programming and Scripting
At times I find the need to test that the tacacs port 49 is open.
The code below works but is painfully slow because I have to wait on the timeouts.
Examples of possible responds
router1#telnet 10.11.20.14 49
Trying 206.112.204.140, 49 ... Open
route1#telnet 10.11.19.14 49
Trying... (1 Reply)
Discussion started by: popeye
1 Replies
7. Shell Programming and Scripting
Hi
I want to create a script that will authenticate user from a file and if both of them match then only the script is allowed to be executed...
Suppose I have a script say test.sh and a file config.txt
for users whose user ids exist in the text file should only be given permission to... (1 Reply)
Discussion started by: ultimatix
1 Replies
8. UNIX for Dummies Questions & Answers
Dear all
I want to redirect the logs of the syslog of a tru64 unix machine in a log and event monitoring tool installed in another server. In the syslog.conf i have appended *.*@<server_name> at the end, where <server_name> is the name of the machine on which the reporting tool is running. I... (0 Replies)
Discussion started by: adak2010
0 Replies
9. HP-UX
Hi all,
I have installed a software on a local machine running UNIX .
Using NetBatch utility, In the COMMUNICATION file on this Local UNIX machine I have added:
remote_machine_name:OS: Description:Type
so that I can use this remote machine running UNIX to complete jobs which are... (0 Replies)
Discussion started by: molly81
0 Replies
TACPLUS.CONF(5) BSD File Formats Manual 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 charac-
ters, 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 seconds for communicating with the server. The timeout applies sepa-
rately 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
# A server using a non-standard port, with an increased timeout and
# the "single-connection" option.
auth.domain.com:4333 "Don't tell!!" 15 single-connection
# A server specified by its IP address:
192.168.27.81 $X*#..38947ax-+=
SEE ALSO
libtacplus(3)
AUTHORS
This documentation was written by John Polstra, and donated to the FreeBSD project by Juniper Networks, Inc.
BSD
July 29, 1998 BSD