Sponsored Content
Special Forums IP Networking Linux Client To Authenticate using TACACS Post 302854825 by Corona688 on Wednesday 18th of September 2013 12:00:55 PM
Old 09-18-2013
TACAS appears to be a Cisco thing these days, but there's software implementations too, some commercial, some not, see TACAS+ on Wikipedia
 

8 More Discussions You Might Find Interesting

1. Cybersecurity

VPN client for linux?...

I'm looking for an open source VPN client that I can set up on RedHat 7.1. Any suggestion? Thanks in advance. VJ :) (3 Replies)
Discussion started by: vancouver_joe
3 Replies

2. Shell Programming and Scripting

Expect/telnet/testing tacacs on a cisco

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

3. UNIX for Advanced & Expert Users

Configuring Unix(FreeSBD) to authenticate to TACACS

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

4. BSD

Configuring Unix(FreeSBD) to authenticate to TACACS

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. Cybersecurity

Configuring Unix(FreeSBD) to authenticate to TACACS

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

6. Linux

MS Exchange from linux client

I haven't seen many updates so im here to ask my fellow *nix users if they have found a way or have atleast heard anything about GUI Mail Client that can access mail from a MS Exchange server. I know that Evolution stopped worked up until Exchange 2003 but not for 2007 or 2010. It doesn't seem... (4 Replies)
Discussion started by: binary-ninja
4 Replies

7. AIX

AIX LDAP client authenticate against Linux Openldap server over TLS/SSL

Hi folks, How can i configure an AIX LDAP client to authenticate against an Linux Openldap server over TLS/SSL? It works like a charm without TLS/SSL. i would like to have SSL encrypted communication for ldap (secldapclntd) and ldapsearch etc. while accepting every kind of certificate/CA.... (6 Replies)
Discussion started by: paco699
6 Replies

8. UNIX for Advanced & Expert Users

Windows AD users authenticate to Linux

Hello folks, Please advise me what is the best way to authenticate Windows AD users against Linux machines. Currently I am going to take a look of Vintela Authentication Services and please let me know if you have experience with VIntela. Thanks in advance (1 Reply)
Discussion started by: Vit0_Corleone
1 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
All times are GMT -4. The time now is 09:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy