03-26-2009
.rhosts should contain the exact server name not an IP address or an alias.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm trying to nohup a job that executes a remote shell on another host but it breaks as soon as I launch it, and I get the following back to my terminal.
+ Stopped (tty input) nohup remsh target_host -l user "ls /proj"
This is the command I'm running.
nohup remsh target_host -l user "ls... (2 Replies)
Discussion started by: tavaresd
2 Replies
2. UNIX for Dummies Questions & Answers
Is there a way to execute more than one command on a remote server using remsh? (2 Replies)
Discussion started by: aaareyes
2 Replies
3. UNIX for Dummies Questions & Answers
i m try to do remsh i need to know what are the step to define the user and password i try .rhosts it give me
operator:/export/home/operator>remsh billmed ps -ef
permission denied
just for testing (3 Replies)
Discussion started by: kazanoova2
3 Replies
4. UNIX for Advanced & Expert Users
Hi All,
We have 2 unix boxes HP UX. From Box1 we need to run a script on Box2 using remsh. The job at Box2 exits with status 0 on successful completion & 1 if fails.
But even if the scrips fails (exits with return status 1) at Box2, the $? get the value 0.
script at Box2 : remote_script.sh... (2 Replies)
Discussion started by: sabyasm
2 Replies
5. Solaris
host Solaris 5.9 E250 host-name: sunsrv1
remote Solaris 5.8 Netra 250 host_name: sspfs_svr
i am able to remsh (or rsh)from remote to host
like ;
$ remsh sunsrv1 uname -n
sunsrv1
but opposite way not possible;
# remsh sspfs_svr ls
sspfs_svr: Connection refused
OR
# rsh -l username... (2 Replies)
Discussion started by: xramm
2 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. HP-UX
Hi,
I can remsh from a HPUX to a UNIX however my function keys dont then work as they should !
Any suggestions ? - have tried creating .kshrc
Thanks (2 Replies)
Discussion started by: belfastbelle
2 Replies
8. Shell Programming and Scripting
Hi All,
Im using remsh to execute shell script on remote server. And this script gets called from another AIX server.
My code is:
remsh $rHost -l $rUser -n "export JAVA_HOME=/usr/java6_64_SR7; export ORACLE_HOME=/oravl01/oracle/11.1.0.7;
export... (3 Replies)
Discussion started by: AB10
3 Replies
9. UNIX for Advanced & Expert Users
Hi
Can any 1 tell me how to use REMSH command with example
actually i wanted to run the following command on different severs thru script "df -k .| tail -1 | tr -s ' ' ' ' | cut -d ' ' -f5" :)
please reply ASAP.:) (3 Replies)
Discussion started by: maddy_07
3 Replies
10. Shell Programming and Scripting
Hello All,
I am on HP-UX.
Problem is that my remote script behaves different depending on execution method.
Method1 (Remote execution):
remsh remoteserver /home/myscript.sh
Method2 (Local execution):
remoteserver :/home#sh myscript.sh
In method 2, I can succesfully set timestamp with... (6 Replies)
Discussion started by: mrcrowley
6 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