03-05-2014
No, you can't do it like this. You would have to use a tool like
expect, but even so, this isn't the best way. Two main alternatives exist:-
- rsh/resh/remsh/rlogin
- ssh
The first set uses plain ASCII text over the network to shake hands with a server that will accept your connection. It must be offering the service of course. You would set up a .rhosts file for the user you are connecting to.
The second is better in many ways and should be preferred if your server offers SSH. You can set up a key-pair and authenticate the client connection request and then usage is much easier and the connection is encrypted (data compression built in if you have lots of output)
What client and server OS and versions are you operating. Do you have any of these services available on the server, or is it really just telnet?
It also depends what you are trying to achieve. is it a true interactive login, or running a command on the server?
Regards,
Robin
Liverpool/Blackburn
UK
10 More Discussions You Might Find Interesting
1. HP-UX
Hi friend,
I'm facing a problem to access the console and telnet to the HP ux 11 server due to the system file is full. How to access this server via single mode and how to mount the folder / and folder /var?
thanks.
vestro (1 Reply)
Discussion started by: vestro
1 Replies
2. Shell Programming and Scripting
Hi,
I have to run a script shell on a unix server from my windows PC. For that, I open a cmd windows and use Telnet to connect to the unix and run the script (by the .profile of a special user). Is it possible to automate Telnet in order to not enter the user and the password ?
Anyway, has... (4 Replies)
Discussion started by: tbeghain
4 Replies
3. Solaris
Hi,
I am unable to login into my terminal hosting Solaris 10 and get the below error message
"Server refused to allocate pty
ld.so.1: sh: fatal: libc.so.1: open failed: No such file or directory "
Is there anyways i can get into my machine and what kind of changes are required to be... (7 Replies)
Discussion started by: sankasu
7 Replies
4. Shell Programming and Scripting
Hi all,
I am currently running a daemon which creates a virtual terminal for testing purposes. Essentially, if I were to interact with it manually, this is what I get.
john@test1:~$telnet localhost 7777
Trying ::1...
Connected to localhost.
Escape character is '^]'
mip6d> pl
eth2... (6 Replies)
Discussion started by: abxccd
6 Replies
5. Shell Programming and Scripting
Hi,
Can anyone pls help me to automate login to cvs. I basically want to login to cvs and update a file.
the script always gets to the login and returns the prompt for a password.
Is there any way to send the password in the script itself.
Here is the script:
#!/bin/ksh... (0 Replies)
Discussion started by: raghu_shekar
0 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I was writing one script which includes to switch to the another telnet automatically from the present telnet server. I was using rlogin but firstly it takes the same user name of the present telnet and secondly it is prompting for the password.
But i want to switch to the another telnet... (2 Replies)
Discussion started by: Prateek
2 Replies
7. HP-UX
why I can login by telnet using root account
but when i use login by ssh using root account
it is not successful ,is it different password
i am sure ssh service is started (2 Replies)
Discussion started by: alert0919
2 Replies
8. Shell Programming and Scripting
Hi All,
I need information regarding how to automate the pbrun process in script in Linux.
Example sample script below,
#!bin/sh
/usr/xyz/pbrun testusr -password testpwd
testusr is username for pbrun and testpwd is password for pbrun.
Im not sure if it is correct way to invoke pbrun in... (2 Replies)
Discussion started by: Pravs4info
2 Replies
9. Shell Programming and Scripting
Hi
I have a script at Server B. I want to run it from server A via another script. I tried the following command. ssh mss@247.123.456.123 "sh pm10.sh"
It's getting login automatically, but while running the script through error like "reppar: command not found" where reppar is an application... (4 Replies)
Discussion started by: rajeshmepco
4 Replies
10. Shell Programming and Scripting
Hello everyone.
I'm a Linux novice trying out a lot of bash scripting lately, as it is so very addictive.
Lately I have been setting up one of my boxes remotely and have been hardening it as much as possible. Please allow me to explain the scenario, as it does tend to become a little... (1 Reply)
Discussion started by: instro
1 Replies
RSHD(8) System Manager's Manual RSHD(8)
NAME
rshd - remote shell server
SYNOPSIS
shell stream tcp nowait root /usr/sbin/in.rshd in.rshd
tcpd shell /usr/sbin/in.rshd
DESCRIPTION
Rshd is the server for the rcmd(3) routine and, consequently, for the rsh(1) program. The server provides remote execution facilities with
authentication based on privileged port numbers from trusted hosts.
Rshd listens for service requests at the port indicated in the ``cmd'' service specification; see services(5). When a service request is
received the following protocol is initiated:
1) The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2) The server reads characters from the socket up to a null (` ') byte. The resultant string is interpreted as an ASCII number, base
10.
3) If the number received in step 1 is non-zero, it is interpreted as the port number of a secondary stream to be used for the stderr.
A second connection is then created to the specified port on the client's machine. The source port of this second connection is
also in the range 0-1023.
4) The server checks the client's source address and requests the corresponding host name (see gethostbyaddr(3N), hosts(5) and
named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used.
5) A null terminated user name of at most 16 characters is retrieved on the initial socket. This user name is interpreted as the user
identity on the client's machine.
6) A null terminated user name of at most 16 characters is retrieved on the initial socket. This user name is interpreted as a user
identity to use on the server's machine.
7) A null terminated command to be passed to a shell is retrieved on the initial socket. The length of the command is limited by the
upper bound on the size of the system's argument list.
8) Rshd then validates the user according to the following steps. The local (server-end) user name is looked up in the password file
and a chdir is performed to the user's home directory. If either the lookup or chdir fail, the connection is terminated. If the
user is not the super-user, (user id 0), the file /etc/hosts.equiv is consulted for a list of hosts considered ``equivalent''. If
the client's host name is present in this file, the authentication is considered successful. If the lookup fails, or the user is
the super-user, then the file .rhosts in the home directory of the remote user is checked for the machine name and identity of the
user on the client's machine. If this lookup fails, the connection is terminated.
9) A null byte is returned on the initial socket and the command line is passed to the normal login shell of the user. The shell
inherits the network connections established by rshd.
DIAGNOSTICS
Except for the last one listed below, all diagnostic messages are returned on the initial socket, after which any network connections are
closed. An error is indicated by a leading byte with a value of 1 (0 is returned in step 9 above upon successful completion of all the
steps prior to the execution of the login shell).
``locuser too long''
The name of the user on the client's machine is longer than 16 characters.
``remuser too long''
The name of the user on the remote machine is longer than 16 characters.
``command too long ''
The command line passed exceeds the size of the argument list (as configured into the system).
``Login incorrect.''
No password file entry for the user name existed.
``No remote directory.''
The chdir command to the home directory failed.
``Permission denied.''
The authentication procedure described above failed.
``Can't make pipe.''
The pipe needed for the stderr, wasn't created.
``Try again.''
A fork by the server failed.
``<shellname>: ...''
The user's login shell could not be started. This message is returned on the connection associated with the stderr, and is not preceded by
a flag byte.
SEE ALSO
rsh(1), rcmd(3).
BUGS
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is
useful in an ``open'' environment.
A facility to allow all data exchanges to be encrypted should be present.
A more extensible protocol should be used.
4.2 Berkeley Distribution May 24, 1986 RSHD(8)