Dear friends..
Our project has a module that runs on handheld devices. Through the handheld we telnet to solaris where the application actually runs. I noticed that after starting a session through the handheld, if i go out of range or if i remove and replace the battery in the handheld, the... (1 Reply)
{
sleep 2
echo "$user"
sleep 2
echo "$password"
sleep 2
echo " ls"
sleep 10
echo "exit"
}| telnet $server
I have a machine x and i have executed the above script on machine 'x'.
i entered the... (6 Replies)
The situation:
a Unix system (UnixWare 7.1.3) to which are connected other systems;
various p.c. on the LAN that they connect Unix to the system via TelNet.
The problem:
I need to intercept the address IP of the p.cs. connected via telnet to the Unix system.
Particularly, I have to know the... (2 Replies)
In either case using ksh or tcl, how can I check that I have a successfule telnet session and am being prompted with a tacacs login prompt ?
:confused:
DOIT () {
sleep 2
echo "<tacacs name >"
sleep 1
echo "<password>"
echo "en"
sleep 1
echo "<enable password>"
echo "term length 512"... (0 Replies)
How can I disconnect an existing telnet session? The host is a serial port server with multiple ports. The users login using the host's name and a port, i.e. telnet host01 1235.
Thanks. (14 Replies)
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Hi,
I search the way to limit, for a group on a AIX 5.3, one telnet session by user (Simultaneous).
I search a lot in /etc/security but the only way found is with the pam authentication that i not use.
No solution found also in smit menu...
Thanks for your help. (2 Replies)
Discussion started by: feilong
2 Replies
LEARN ABOUT ULTRIX
rlogind
rlogind(8c)rlogind(8c)Name
rlogind - remote login server
Syntax
/etc/rlogind
Description
The server is used for the program. The server provides a remote login facility with authentication based on privileged port numbers.
The server is invoked by when it receives a connection on the port indicated in the login service specification. For further information,
see 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. 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, allocates a pseudo terminal and manipulates file descriptors so that the slave half of
the pseudo terminal becomes the stdin, stdout, and stderr for a login process. For further information, see
The login process is an instance of the program, invoked with the option. The login process then proceeds with the authentication process
as described in but if automatic authentication fails, it reprompts the user to log in on a standard terminal line.
The parent of the login process manipulates the master side of the pseudo terminal, operating as an intermediary between the login process
and the client instance of the program. In normal operation, the packet protocol described in 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. For further information see
The screen or window size of the terminal is requested from the client, and any changes in the window size from the client are sent to the
pseudo terminal.
Restrictions
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but it is
useful in an open environment.
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.
Hostname for your address unknown
No entry in the host name database existed for the client's machine.
Try again
A fork by the server failed.
/bin/sh: ...
The user's login shell could not be started.
See Alsorlogin(1c), inetd(8c)rlogind(8c)