09-26-2014
Also, you don't cram passwords into ssh, you use
ssh keys.
This User Gave Thanks to Corona688 For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi everybody,
im kinda a new to scripting....
i have attached an image in this post...
my goal is to extract data from the remote servers (server1,2,3 as in figure)
to the server residing locally....
the criterias are:
* I should not pass the password across the remote servers.
*... (1 Reply)
Discussion started by: mercuryshipzz
1 Replies
2. UNIX for Advanced & Expert Users
Hi,
I have web server (apache) installed in server-1 and i want to view the web pages from diferent servers also while the web server is running only in one server ....(all the servers are connected to office LAN)
right now all the servers have apache running......and CPU utilzation is at its... (2 Replies)
Discussion started by: aditya.ece1985
2 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I Installed Tomcat in an remote linux server (/usr/tomcat)and start service, using ./startup.sh (and tried with ./catalina.sh too).
//----------------------------------------------------------------//
# ./startup.sh
Using CATALINA_BASE: /usr/tomcat/apache-tomcat-6.0.16/
Using... (1 Reply)
Discussion started by: gothama
1 Replies
4. UNIX for Dummies Questions & Answers
I am trying to setup an FTP server in a Fedora Core 3 machine through the command line interface and not KDE.
I think I am successful in getting the ftp service running, as when I do an ftp 127.0.0.1, I am able to log in using any one the user accounts I have created on this machine and browse... (8 Replies)
Discussion started by: cooljumbo2k8
8 Replies
5. Shell Programming and Scripting
Hi,
Im creating a script that is supposed to run commands on remote server using sftp.
My script is as below:
#!/bin/ksh
sftp remote_server
mypassword
cd /u08/mydir/allfiles
mget *
..
But this is what I got when I runned the script:
Connecting to remote server...... (3 Replies)
Discussion started by: luna_soleil
3 Replies
6. UNIX for Dummies Questions & Answers
server is at remote site; server is up. I can access it through console. but I cannot access it through ssh. I have restarted SSH already and even do ifconfig ce0 down and up
still not successful ... any comment? (2 Replies)
Discussion started by: uuontario
2 Replies
7. OS X (Apple)
Good evening
I have a VPS Server
Processor OS: centos-5-x86
I could not log on to the SSH Server
This image from the panel WHM
Main >> Server Status >> Service Status
https://www.unix.com/attachment.php?attachmentid=1666&stc=1&d=1286598999
This copy of the program PuTTY
... (4 Replies)
Discussion started by: hamed
4 Replies
8. UNIX for Advanced & Expert Users
Hi!
I came to know about SSH Tunneling to bypass the Firewall.
I will have to setup a free access SSH server to tunnel data access through PUTTY or OpenSSH.
The problem is that I don't know about any free access servers.
So, can anyone of you guide me for that, for any type of help? (1 Reply)
Discussion started by: nixhead
1 Replies
9. IP Networking
I need to do some remote administration to an access point that is sitting behind a firewall that only has ssh enable from the outside but http/https from the inside. So to be a bit clearer:
remote(outside firewall) ssh --> ssh-server(internal) --> access point(http/https)
Ultimately... (3 Replies)
Discussion started by: metallica1973
3 Replies
10. Shell Programming and Scripting
Hi All
I need to transfer a file from a UNIX server to a windows server.
I saw that it is possible to do this using scp command by looking at the forum listed below:
... (2 Replies)
Discussion started by: vx04
2 Replies
LEARN ABOUT MINIX
rlogind
RLOGIND(8) System Manager's Manual RLOGIND(8)
NAME
rlogind, in.rld - remote login server
SYNOPSIS
login stream tcp nowait root /usr/sbin/in.rld in.rld
tcpd login /usr/sbin/in.rld
DESCRIPTION
Rlogind is the server for the rlogin(1) program. The server provides a remote login facility with authentication based on privileged port
numbers from trusted hosts.
Rlogind listens for service requests at the port indicated in the ``login'' 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 checks the client's source address and requests the corresponding host name (see gethostbyaddr(3), hosts(5) and
named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used.
Once the source port and address have been checked, rlogind allocates a pseudo terminal (see tty(4)), and manipulates file descriptors so
that the slave half of the pseudo terminal becomes the stdin , stdout , and stderr for a login process. The login process is an instance
of the login(1) program, invoked with the -r option. The login process then proceeds with the authentication process as described in
rshd(8), but if automatic authentication fails, it reprompts the user to login as one finds on a standard terminal line.
The parent of the login process manipulates the master side of the pseduo terminal, operating as an intermediary between the login process
and the client instance of the rlogin program. In normal operation, the packet protocol described in tty(4) is invoked to provide ^S/^Q
type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and
terminal type, as found in the environment variable, ``TERM''; see environ(7). The screen or window size of the terminal is requested from
the client, and window size changes from the client are propagated to the pseudo terminal.
SEE ALSO
rlogin(1).
DIAGNOSTICS
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1.
``Try again.''
A fork by the server failed.
``/bin/sh: ...''
The user's login shell could not be started.
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 RLOGIND(8)