03-30-2009
rcp works as rsh . so make sure u can logon to the dest machine via rsh.
It typically uses the TCP/IP protocol and the .rhosts file for authentication.So you also check the entry in .rhosts file(in the dest server) if you are authorized to that remote machine
10 More Discussions You Might Find Interesting
1. Cybersecurity
Now I want to copy a directry from Sco Unix at Windows NT 4.0 with Sp6. But I always meet the Permision Refuse error.
I need your help. GOD
Thank you very much. (1 Reply)
Discussion started by: livic
1 Replies
2. HP-UX
Hi,
Can anyone help me to trace who has made rcp to a HP-UX machine? Is there a file that keeps such records? I know ftp's are recorded in /var/adm/syslog but i only need rcp.Thanks... (0 Replies)
Discussion started by: ilkergu
0 Replies
3. UNIX for Dummies Questions & Answers
I am trying to set up RCP so root can access a few machines for file transfer. On the target machine, I have set up a .RHOSTS file that looks like:
10.33.1.59 root
However when I try to use RCP to copy a file to this machine, I get permission denied. Is it possible since another user is... (1 Reply)
Discussion started by: hshapiro
1 Replies
4. Solaris
I applied patch 108993-65 on two servers (5.8) and now I am unable to rcp to either machine. Getting "permission denied". (3 Replies)
Discussion started by: shorty
3 Replies
5. HP-UX
Hi,
Good day to you all. I am trying to use rcp command to transfer some files on the remote machine. I have already setup .rhosts on my server and on the remote machine. When I do rcp I get this error message
rcmd_af: Lost connection
Is anybody familiar with this one? Thanks in advance.
... (3 Replies)
Discussion started by: sodapop
3 Replies
6. UNIX for Advanced & Expert Users
Hi,
The B machine is using rcp method to copy a file to A machine.
But it is not getting copied.
Its giving the error as:
remshd: Login incorrect.
On A machine rhosts file has details about the B machine.
Could anyone tell what could be done to make this work?
Any help is appreciated.... (1 Reply)
Discussion started by: nehak
1 Replies
7. Shell Programming and Scripting
Hi
I am using rcp command to copy the file one linux to other linux machine
I need the ouput log for this
like 1 file coied
size of the file
date stamp
my copy comman is
rcp 10.100.11.2:/u01/pr/uni.txt /u05/ryd/uni.txt
once this script run
i need to capture the... (3 Replies)
Discussion started by: aboorkuma
3 Replies
8. UNIX for Dummies Questions & Answers
hi,
When i use RCP command to copy filr from a different servers, it is showing as connection refused???
ca anyone help me out???
thanks,
Arun Manas:b: (2 Replies)
Discussion started by: arunmanas
2 Replies
9. Solaris
hi everybody ,
i have a problem with rcp between too hosts :
when i do :
host 1(root) :# rcp file1 host2:/target2
or :
host2 (root):#rcp file2 host1:/target1
i have the following message : permission denied
I made the following changes, but the problem still persists :
I added the... (0 Replies)
Discussion started by: lid-j-one
0 Replies
10. Shell Programming and Scripting
what different between two instruction
cp -r
rcp -r (1 Reply)
Discussion started by: tamer11007
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