10 More Discussions You Might Find Interesting
1. AIX
Hi all, just after a bit of help..
I am attempting to read in the contents of a flat text file from one system to another using 'rsh', i have this setup over around 15 machines and it works for them all except one. On this one machine it just reads in a blank line for some reason. The machine... (21 Replies)
Discussion started by: forefather1977
21 Replies
2. UNIX for Dummies Questions & Answers
Hello,
When I try and RSH/RLOGIN onto a box with user root, I get the prompt but the username/password combination NEVER work. I have the password up properly on the host machine. Does rsh/rlogin not make use of ./etc/passwd and /etc/shadow? (1 Reply)
Discussion started by: mojoman
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have an old solaris 2.6 box and I need to copy all the data from the hard drive onto another machine. It does not have ssh installed so I am forced to use rsh. My plan was to execute the rcp command from the solaris box to a Centos 5 machine. I have installed rsh client and server on my... (1 Reply)
Discussion started by: mojoman
1 Replies
4. Shell Programming and Scripting
I am trying to connect to a remote server using rsh.
first i have given the following command.
$ rsh 242.13.45.54 -l
now i got the following message
"connect to address 242.13.45.54: Connection refused
Trying krb4 rlogin...
connect to address 242.13.45.54: Connection refused
trying... (1 Reply)
Discussion started by: ravi raj kumar
1 Replies
5. Shell Programming and Scripting
On a SUN cluster (ksh - Solaris 8 SPARC) I run a script which at some time has to perform a rsh command on the alternate node but with some other user (let's say "oper") so it should be like:
rsh su - oper -c APP_COMMAND -paramters
When I run the script APP_COMMAND is done but without taking... (2 Replies)
Discussion started by: heartwork
2 Replies
6. Shell Programming and Scripting
I tried to execute by rsh a script, but I did not succeed.
You can execute only commnads (not scripts) by rsh or there are some other restrictions?!?
root@a1 #pwd
/
root@a1 #rsh a2 monitor
ksh: monitor: not found
On the other hand:
root@a1 #rsh a2
root@a2 #pwd
/
root@a2 #ls monitor... (9 Replies)
Discussion started by: heartwork
9 Replies
7. Shell Programming and Scripting
hey,
I'v a problem when I use rsh. When it logs in, it goes my home directory. I want it to go directly to my working directory. An idea I had was to redirect pwd to a file (pwd > somefile) and then once I'v rsh'd, cd to that path. I don't know how to read from the file to use as a parameter for... (2 Replies)
Discussion started by: Bacchus
2 Replies
8. UNIX for Dummies Questions & Answers
Hello,
I am currently trying to execute a command in a Windows machine from a UNIX server. In order to do this, I am using the RSH command in UNIX but whenever i do this I am getting this error "RSHD: <username>: could not retrieve password: Please login and run rsetup."
I log in via the... (0 Replies)
Discussion started by: punyenye
0 Replies
9. Shell Programming and Scripting
Hi,
I am using rsh command in scripting. But I wan to run the script as a bg process.
When I run the script, it says stopped.
My doubt is ....if I use the rsh in scripting ......bg is possible or not ???
EX: test-rsh
rsh 172.16.73.38 df -k >DF.log
Result when I run this script ... (5 Replies)
Discussion started by: vastare
5 Replies
10. UNIX for Dummies Questions & Answers
Hi all
I have checked the archives and cannot find a solution.
I get a permission denied error, however all the suggestions donot help.
here is the scenario
root@OPSBOX#/>rsh OPSBOX ls -l
rshd: 0826-813 Permission is denied.
root@OPSBOX#/>pg .rhosts
OPSBOX root
OPSBOX ... (1 Reply)
Discussion started by: jhansrod
1 Replies
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