05-07-2002
a- Add the IP, host_name and aliases in the /etc/hosts in both machines.
In the AIX machine
if [ ! f /etc/netsvc.conf ]
then
echo "hosts=local,bind" > /etc/netsvc.conf
else
echo "review the hosts definitions in the /etc/netsvc.conf"
echo "hosts=local,bind"
fi
In the linux machine:
in the /etc/nsswitch.conf
hosts: files dns
b- Add the .rhosts in the home directory of the user in both machines:
example for root:
linux box:
echo "server_aix root" >> $HOME/.rhosts
aix box:
echo "server_linux root" >> $HOME/.rhosts
c- Permit the root login in both machines
linux box:
Add the apropiate entry in the /etc/securetty
aix box:
chuser login=true rlogin=true root
Good luck. Hugo.
10 More Discussions You Might Find Interesting
1. UNIX Desktop Questions & Answers
When i start my pc after the installation of suse linux it ask me for resolution but not for graphical interface, for console, can i run a command to change it again?
Thanx! (3 Replies)
Discussion started by: Linux_fan
3 Replies
2. UNIX for Advanced & Expert Users
My machine (Sun Blade 100) has just had it's OS reinstalled (solaris 8). For some reason the monitor resolution has changed (decreaded so that I have less monitor real esate).
Does anybody know the command to change monitor resolution in Solaris?
Cheers
AreaMan (2 Replies)
Discussion started by: AreaMan
2 Replies
3. UNIX for Advanced & Expert Users
Guys,
We are going to order the wide screen monitor with 1920*1200 resolution for one U60 in our client side, that their current graphic card is Elite3D-m6 and the higher resolution which this card supports is 1280*1024.
I just want to make sure wehther we are able to work with this monitor via... (1 Reply)
Discussion started by: nikk
1 Replies
4. Solaris
Hi,
I got solaris 10 installed on a E250 and i am expericing issues resolving dns.
from some research i think it's becuase where i haven't set-up NIS and i don't intend too as i am just setting up a box to poke communigate pro.
Any help or advice please?
Thanks in advance
Alan (1 Reply)
Discussion started by: e250user
1 Replies
5. IP Networking
I have an AIX4.3 box on our subnet, called LIMEST3.OURDOMAIN.CO.UK, with IP address 10.103.1.13
It has the following entry in its own /etc/hosts:
10.103.1.13 limest3 limest3.ourdomain.co.uk
Now, if I ping limest3.ourdomain.co.uk or ping 10.103.1.13, the result is instant. However if I ping... (4 Replies)
Discussion started by: grimbleshanks
4 Replies
6. Solaris
Hi friends, i had small problem in my home pc i install solaris 10 but GUI is very big cannot view any thing, but i can open terminal where with very difficulty is there any command to re size my resolution some thing like 1024. if not i want to log in default console other than GUI only terminal... (5 Replies)
Discussion started by: kurva
5 Replies
7. Solaris
how to change screen resolution in CDE prompt (2 Replies)
Discussion started by: tirupathi
2 Replies
8. Solaris
Hi all. I have a very peculiar problem in Solaris 10. The output of the m64config -prconf command with regards the Card Adapter is the following.
Card possible resolutions: 720x400x85, 640x480x60, 640x480x72, 640x480x75
800x600x56, 800x600x60, 800x600x72, 800x600x75, 1024x768x60
... (0 Replies)
Discussion started by: lynxman
0 Replies
9. Windows & DOS: Issues & Discussions
Hello guys,
At windows 7, when multiple ip addresses used on one nic, starting "network" from desktop is able to resolve samba machine's name (freebsd + samba3.5.9 from ports) but does not want to open machine (error: unexisting) nor ping it by name. Works fine if specified by ipv4/ipv6 address... (2 Replies)
Discussion started by: hachik
2 Replies
10. Solaris
I have problem with oracle solaris 10 running on oracle sparc T4-2 server.
Os information: 5.10 Generic_150400-03 sun4v sparc sun4v
Output from tcpstat.d script
TCP bytes: out outRetrans in inDup inUnorder
6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies
LEARN ABOUT NETBSD
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, ``+@netgroup'' (from
which only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, ``+@netgroup'' (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD