07-21-2011
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
9 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. 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
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. BSD
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
7. 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
8. 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
9. 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
nfssec(5) File Formats Manual nfssec(5)
NAME
nfssec - overview of NFS security modes
DESCRIPTION
The mount_nfs(1M) and share_nfs(1M) commands each provide a way to specify the security mode to be used on an NFS filesystem through the
option. mode can be either or These security modes may also be added to the automount maps. Note that mount_nfs(1M) and automount(1M) do
not support at this time.
The option on the share_nfs(1M) command line establishes the security mode of NFS servers. If the NFS connection uses the NFS Version 3
protocol, the NFS clients must query the server for the appropriate mode to use. If the NFS connection uses the NFS Version 2 protocol,
then the NFS client uses the default security mode, which is currently NFS clients may force the use of a specific security mode by speci-
fying the option on the command line. However, if the filesystem on the server is not shared with that security mode, the client may be
denied access.
If the NFS client wants to authenticate the NFS server using a particular (stronger) security mode, the client wants to specify the secu-
rity mode to be used, even if the connection uses the NFS Version 3 protocol. This guarantees that an attacker masquerading as the server
does not compromise the client.
The NFS security modes are described below. Of these, the modes use the Kerberos V5 protocol for authenticating and protecting the shared
filesystems. Before these can be used, the system must be configured to be part of a Kerberos realm.
Use authentication. The user's UNIX user-id and group-ids are passed in the clear on the network, unauthenticated by the NFS server
. This is the simplest security method and requires no additional administration. It is the default used by HP-UX NFS Version 2
clients and HP-UX NFS servers.
Use a Diffie-Hellman public key system
which is referred to as in the forthcoming Internet RFC).
Use Kerberos V5 protocol to authenticate users before granting access
to the shared filesystem.
Use Kerberos V5 authentication with integrity checking (checksums) to
verify that the data has not been tampered with.
User Kerberos V5 authentication, integrity checksums, and privacy protection
(encryption) on the shared filesystem. This provides the most secure filesystem sharing, as all traffic is encrypted. It should
be noted that performance might suffer on some systems when using depending on the computational intensity of the encryption
algorithm and the amount of data being transferred.
Use null authentication
NFS clients using have no identity and are mapped to the anonymous user by NFS servers. A client using a security mode other
than the one with which an HP-UX NFS server shares the filesystem has its security mode mapped to In this case, if the filesystem
is shared with users from the client are mapped to the anonymous user.
WARNINGS
lists the NFS security services. Do not edit this file. It is not intended to be user-configurable.
FILES
NFS security service configuration file
SEE ALSO
automount(1M), mount_nfs(1M), share_nfs(1M), rpc_clnt_auth(3N), secure_rpc(3N), nfssec.conf(4).
nfssec(5)