Sponsored Content
Full Discussion: tcpwrapper issues
Top Forums UNIX for Dummies Questions & Answers tcpwrapper issues Post 33069 by yls177 on Sunday 15th of December 2002 09:53:52 PM
Old 12-15-2002
success!!

http://www.cert.org/security-improve...s/i041.07.html

download from here.

3) edit the Makefile which is in your unpacked files directory
3.1) add CC=/usr/loca/bin/gcc
3.2) comment REAL_DAEMON_DIR=/usr/libexec
3.3) u need either gcc or cc compiler!
4) make sunos5 (different OS matters here)
4.1) enter make to get a list of available OS
5) after a successful make, copy the programs as belows
$ cp tcpd /usr/sbin

$ cp safe_finger /usr/sbin

$ cp tcpdchk /usr/sbin

$ cp tcpdmatch /usr/sbin

$ cp try-from /usr/sbin

$ cp hosts_access.3 /usr/man/man3

$ cp hosts_access.5 /usr/man/man5

$ cp hosts_options.5 /usr/man/man5

$ cp tcpd.8 /usr/man/man8

$ cp tcpdchk.8 /usr/man/man8

$ cp tcpdmatch.8 /usr/man/man8

6) edit
6.1) hosts.allow (this is from saetra, the new Sun server)
#ALL : ALL
ALL : 127.0.0.1
in.telnetd : list of ips

in.ftpd : list of ips
6.2) hosts.deny
ALL:ALL
7) tcpdchk , tcpdmatch to check the configuration of the files.
7.1) tcpdchk -- to check the entires in the two files
7.2) tcpdmatch - to check the services and the host
example : tcpdmatch in.telnetd list of ips
8) kill -HUP <pid of inetd>
yls177
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

SU issues

Hi, I have automated a build process that does the following activities. 1. check out code from cvs to a specific directory 2. build the revision checked out with 'ANT' 3. integrate the compiled code with the QA/UAT or new environment (/apps/QA or /apps/UAT or /apps/new directory) I... (1 Reply)
Discussion started by: yoi2hot4ya
1 Replies

2. Shell Programming and Scripting

while loop issues

Hi guys, Been sifting through these forums for awhile, but never had an account or needed to post. Shoutouts to a great forum with heaps of useful info. Now i consider myself a noob when it comes to linux and to bash scripting. I recently started to learn to use Vmware ESX server which uses... (4 Replies)
Discussion started by: ryath
4 Replies

3. Solaris

Issues with ldd

I tried to compile php and integrate it into apache on solaris. It compiled ok and I created a package. If I install it on a system that has the libpng from sunfreeware, it wants to use that library instead of the system SUNWpng. It doesn't run using SMCpng, but it runs using the system SUNWpng.... (4 Replies)
Discussion started by: Mike_the_Man
4 Replies

4. Shell Programming and Scripting

Issues with grep -w

I am trying to use grep -w something as shown below. grep -w "$a" $LOG1 It is not giving me neither any error nor any data. I am facing the issue while i run this command inside a script. But i am getting the data if i run the above command outiside the script. here $a=08/11/2009 21 i... (13 Replies)
Discussion started by: rdhanek
13 Replies

5. AIX

lpstat issues

Hi, I tried to migrate a server, I installed AIX on a new server and I want to configure the printer queues. I copied all of files from the old server where the printer queues are working fine. I followed these steps: 1. copy the /etc/qconfig (make a copy of the original before) 2. Copy the... (10 Replies)
Discussion started by: imad77
10 Replies

6. Shell Programming and Scripting

Issues with Expect

Here is a snippet of code that work for me: expect "abc" {send_log "abc found" } \ "def" {send_log "def found" } \ "123" {send_log "123 found} however the following does not and according to the book "Exploring Expect" it should be equivalent: expect { "abc"... (1 Reply)
Discussion started by: twk
1 Replies

7. Emergency UNIX and Linux Support

rm -rf issues

We are using the solaris server and if i am using rm -rf to delete the directories its asking the confirmation for each and every file inside the directory.Is there any way to disable ( should not ask the confirmation) only for a particular session? (12 Replies)
Discussion started by: sureshbabuc
12 Replies

8. Shell Programming and Scripting

Issues when dividing

Hi, I do have a very simple task to divide 2 variables and display the result. I CANNOT use bc when i try var1=2 var2=4 var3=$(($var1 / $var2)) echo $var3 the output is always 0 What can I change to get a dotted decimal result such as 0.5 ? Thanks! (5 Replies)
Discussion started by: svetoslav_sj
5 Replies

9. Shell Programming and Scripting

Function Issues

I am converting English letters/words/punctuation in leet speak. My current script works just fine, but when I call the functions it seem to be bypassing my second function altogether. I am new to shell scripting so excuse me if its an easy fix. Also, when using SED for whole word phrases like... (4 Replies)
Discussion started by: bri09
4 Replies
HOSTS.EQUIV(5)                                               Linux Programmer's Manual                                              HOSTS.EQUIV(5)

NAME
hosts.equiv - list of hosts and users that are granted "trusted" r command access to your system DESCRIPTION
The file /etc/hosts.equiv allows or denies hosts and users to use the r-commands (e.g., rlogin, rsh, or rcp) without supplying a password. The file uses the following format: +|[-]hostname|+@netgroup|-@netgroup [+|[-]username|+@netgroup|-@netgroup] The hostname is the name of a host which is logically equivalent to the local host. Users logged into that host are allowed to access like-named user accounts on the local host without supplying a password. The hostname may be (optionally) preceded by a plus (+) sign. If the plus sign is used alone, it allows any host to access your system. You can explicitly deny access to a host by preceding the hostname by a minus (-) sign. Users from that host must always supply additional credentials, including possibly a password. For security reasons you should always use the FQDN of the hostname and not the short hostname. The username entry grants a specific user access to all user accounts (except root) without supplying a password. That means the user is NOT restricted to like-named accounts. The username may be (optionally) preceded by a plus (+) sign. You can also explicitly deny access to a specific user by preceding the username with a minus (-) sign. This says that the user is not trusted no matter what other entries for that host exist. Netgroups can be specified by preceding the netgroup by an @ sign. Be extremely careful when using the plus (+) sign. A simple typographical error could result in a standalone plus sign. A standalone plus sign is a wildcard character that means "any host"! FILES
/etc/hosts.equiv NOTES
Some systems will honor the contents of this file only when it has owner root and no write permission for anybody else. Some exceptionally paranoid systems even require that there be no other hard links to the file. Modern systems use the Pluggable Authentication Modules library (PAM). With PAM a standalone plus sign is considered a wildcard character which means "any host" only when the word promiscuous is added to the auth component line in your PAM file for the particular service (e.g., rlogin). EXAMPLE
Below are some example /etc/host.equiv or ~/.rhosts files. Allow any user to log in from any host: + Allow any user from host with a matching local account to log in: host Note: the use of +host is never a valid syntax, including attempting to specify that any user from the host is allowed. Allow any user from host to log in: host + Note: this is distinct from the previous example since it does not require a matching local account. Allow user from host to log in as any non-root user: host user Allow all users with matching local accounts from host to log in except for baduser: host -baduser host Deny all users from host: -host Note: the use of -host -user is never a valid syntax, including attempting to specify that a particular user from the host is not trusted. Allow all users with matching local accounts on all hosts in a netgroup: +@netgroup Disallow all users on all hosts in a netgroup: -@netgroup Allow all users in a netgroup to log in from host as any non-root user: host +@netgroup Allow all users with matching local accounts on all hosts in a netgroup except baduser: +@netgroup -baduser +@netgroup Note: the deny statements must always precede the allow statements because the file is processed sequentially until the first matching rule is found. SEE ALSO
rhosts(5), rlogind(8), rshd(8) COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the latest version of this page, can be found at https://www.kernel.org/doc/man-pages/. Linux 2015-07-23 HOSTS.EQUIV(5)
All times are GMT -4. The time now is 10:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy