02-24-2009
hi
create .rhosts file in /
put + in first line of the file...
we can use hostname too...
try this... revert back...
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am trying to perform a remote tape backup from one SCO openserver to another remote SCO Openserver which happens to have a tape drive configured.
I have added entries into host.equiv and .rhosts on the tape drive server:
prodution_server root # This is equivalent to the hostname and... (1 Reply)
Discussion started by: cstovall
1 Replies
2. Shell Programming and Scripting
i have two main servers which are both hpux. the problem is that i only have single dat drive to use with my backup (using tar command). it always takes me alot of time to perform this activity since the backup can only be done one at a time. there are other hpux box with a dat drive attached on... (3 Replies)
Discussion started by: inquirer
3 Replies
3. Solaris
I am currently using tar to backup a server that has 9gb of data.
This is fine and works fine, as part of this I send the backup to a remote tape on a remote server using rsh..
This is not very secure though is it?
Whats the best idea here - is there another way I should do this to be more... (1 Reply)
Discussion started by: frustrated1
1 Replies
4. UNIX for Dummies Questions & Answers
Hi there: I'm new here
Can anyone help me:
I have DS15 Alpha server : Unix 5.1B
Now i need to connect a DLVT VS80 1U Rackmount Tape Drive unit.
What is the exact comman to mount the DLTape IV??
How do i make backuo @ copy file to the tape?
Thanx to all (0 Replies)
Discussion started by: ayzeayem
0 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I performed backup on tape and I want to append more files to my previous backup on the same backup tape. But before I do that I need to know the backup file size of the first backup I performed so that I know the available size on the backup tape. Can someone help me what command I will use... (0 Replies)
Discussion started by: ayhanne
0 Replies
6. Solaris
Hello Everybody
I have two servers, name A & B. I need to take a backup of one directory(/girish) on serverA. But my tape drive is in serverB through tar command. But when I run the following command it doesn't take the backup. Could any one correct my command to take a backup
tar cvf - ... (0 Replies)
Discussion started by: girish.batra
0 Replies
7. Solaris
Hello all,
I'm trying to backup some files on a solaris 10 machine to the remote tape drive connected to another solaris 10 machine.
I have set up rsh to allow for password-less connection between the servers, but I'm not able to write to the tape with the command:
root@sdp4a>tar cvf... (1 Reply)
Discussion started by: kerrygold
1 Replies
8. UNIX for Dummies Questions & Answers
Hi all,
I've got two HP machines running HP-UX 11.31 and would like to remotely backup one server onto another server's tape unit using the cpio command.
The two servers use a secured communication channel, i.e ssh.
Kindly help,
Koketso (1 Reply)
Discussion started by: Koketso
1 Replies
9. AIX
Hi all
The situation is as follows:
We need to take an mksysb image from an AIX 6.1 server. From some reason (irrelevant to this discussion) this server does not have access to a local CD-ROM or a tape drive. We do have another server with AIX 6.1 (but different technology level) which got access... (1 Reply)
Discussion started by: abohmeed
1 Replies
10. Shell Programming and Scripting
Hi,
Given addresses of 2 remote machines, using a shell script is it possible to
get the state of running processes in "src"
stop all the processes in "src"
exit out of "src"
ssh into "dest"
resume the state of executing processes captured in step 1 in "dest"
Assumption:
"src" is... (3 Replies)
Discussion started by: Saeya Darsan
3 Replies
LEARN ABOUT OSX
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