03-18-2008
It is simple configuration. Suppose you have two hosts, hostA and hostB.
From hostA, you want to do remsh on hostB. Then in hostB, create a file /etc/hosts.equiv and put hostA in hosts.equiv. But this user equivalency will work if the user with which you are logged in on hostA exists on hostB with same mnemonic name.
Note: If you are logged in as root on hostA then /etc/hosts.equiv will not work. Instead create .rhosts in the root directory of root on hostB.
Hope this helps.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is there any problems of binaries compatibility between HPUX 10.20 et 11 ? (2 Replies)
Discussion started by: Olivier
2 Replies
2. HP-UX
Hi everyone!
I need your help.
When i run ipcs -m -a for display shared memory status i see an entry with key 0xdeadbeef:
IPC status from /dev/kmem as of Tue Feb 3 15:55:14 2004
T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME ... (3 Replies)
Discussion started by: andryk
3 Replies
3. HP-UX
:( i got couple of weeks ago a : HP Visualize workstation , model B100.
everithing is ok in the box the only problem is that i 'am not familiar with this operational sys, and i try to uninstall and see if i can get on it windows net server 64 bit. or any other 64 bit operational sys that i'll... (1 Reply)
Discussion started by: newbird
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I am a SAP Basis admin recentely been asked to administer a HPUX server. Could someone recommend some good study material to learn with the Sap
prespective.
-carry (1 Reply)
Discussion started by: carryclare
1 Replies
5. AIX
I know that IBM's official stance is that NIM does not work on etherchannel environment, but has anyone able to get around it?
I'm working on a p5-590 LPAR system, and the NIM master and clients are all on the same frame.
Any help is appreciated. (1 Reply)
Discussion started by: pdtak
1 Replies
6. HP-UX
Hi,
I am trying to remsh from a HPUX to another unix server
What is happening is I cant run commands on the other server
ie
I can
remsh <remoteserver> -l <remotelogin>
but I cant
remsh <remoteserver> -l <remotelogin> -n pwd
getting error message
rshd: 0826-826 The host name for... (3 Replies)
Discussion started by: belfastbelle
3 Replies
7. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
8. Shell Programming and Scripting
Hello.
I cant figure out how can i move entire row up , so it pasted on the one above at the end , or to do that for one character.
In notepads,word, or some other text editors we would do that with backspace button.
Example.
Content of my text file is this :
I am trying to do
that.
And... (2 Replies)
Discussion started by: tonijel
2 Replies
9. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
10. Shell Programming and Scripting
Hello All
Why is hpux is not much spoken in the unix/Linux platform. what is the disadvantes in HPUX
Thanks,
VJ (1 Reply)
Discussion started by: Vijaykannan T
1 Replies
LEARN ABOUT MOJAVE
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