05-06-2011
Does the remote host allow root login?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
Just recently we seem to be getting the following error message relating to SSH when we run the UNIX script in background mode:
warning: You have no controlling tty. Cannot read confirmation.^M
warning: Authentication failed.^M
Disconnected; key exchange or algorithm negotiation... (1 Reply)
Discussion started by: budrito
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
What the problem is that we have a client that has now decided to use SSH protocol 2 only for their internal security audit. This is not a problem except now our SCO system will not connect.
I can connect with putty from a windows box fine until the SCO system tries to access which then... (0 Replies)
Discussion started by: Bilb
0 Replies
3. UNIX for Advanced & Expert Users
Hi
I am using ssh and facing problem. When I execute a command which is my application specific it hangs after giving initial message.Program does not return to command prompt but process is completed in background.
e.g I run following command
$ dtsbackup... (4 Replies)
Discussion started by: shreedhar_tase
4 Replies
4. Shell Programming and Scripting
Hi
Please help me with the following problem with my script.
The following block of code is not repeating in the while loop and exiting after searching for first message.
input_file
==========
host001-01
host001-02
2008-07-23 13:02:04,651 ConnectionFactory - Setting session state... (2 Replies)
Discussion started by: pcjandyala
2 Replies
5. Red Hat
Hey,
I have a Red Hat 5.2 machine with :
2.6.18-92.el5 kernel
PRM's:
openssh-4.3p2-29.el5
openssh-clients-4.3p2-29.el5
openssl-0.9.8e-7.el5
openssh-server-4.3p2-29.el5
openssl-0.9.8b-10.el5
openssl-devel-0.9.8e-7.el5
openssh-askpass-4.3p2-29.el5
I'm trying to transfer files to a... (2 Replies)
Discussion started by: eliraza6
2 Replies
6. Shell Programming and Scripting
Hello All,
Iam using the following command to get the details from a remote server.
ssh server2 su - mqm -c "sh /var/mqm/test1.sh"
The control will not come out once I run this command.
I have set up the required public/private key between server1 and server2 and it works... (3 Replies)
Discussion started by: balaji83it
3 Replies
7. Shell Programming and Scripting
Hello,
i have 10 machines, machine A execute this script:
This is my script:
nb_lignes=`wc -l $1 | cut -d " " -f1`
for i in $(seq $(($nb_lignes - 1)) )
do
machine=`head $1 -n $i | tail -1`
machine1=`head $1 -n $nb_lignes | tail -1`
ssh root@$machine -x " scp /home/file.txt... (7 Replies)
Discussion started by: chercheur857
7 Replies
8. Solaris
Hi guys.
I am using VirtualBox to run Solaris on my host (Windows 7) .
I have setup networking and am able to ping from Solaris to Windows 7 and vice versa.
Now I want to be able to SSH from Windows 7 to my guest (Solaris)
On solaris , the output to
ps -ef | grep ssh shows:
... (8 Replies)
Discussion started by: Junaid Subhani
8 Replies
9. Red Hat
Hi ,
I have done the following things, but still i am not able to connect remote system without enter password.
steps:
1) ssh-keygen -t rsa
2) transfered id_rsa.pub file into remote server.
3) I hve redirect id_rsa.pub content to authorized_keys file.
Note: I have done the same in another... (6 Replies)
Discussion started by: maniapr08
6 Replies
10. Shell Programming and Scripting
I am able to login to server x from y in shell script. But after that command is get executed on server y. I need the command to be executed on server x.
Ex.
ssh -n 0.0.0.X
ls -ltr
Above script I am executing from 0.0.0.Y
I got result but it executed on server Y server. But when I use ssh... (4 Replies)
Discussion started by: babapatil14
4 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