08-23-2011
10 More Discussions You Might Find Interesting
1. IP Networking
Hello All
I am running redhat linux 7.2 and would like to know how i can block telnetting to a specified port .
say for example i would like to block telnet acesses to port 80.
regards
Xiamin (5 Replies)
Discussion started by: xiamin
5 Replies
2. Solaris
dear all
does any one give any user write permission using access control list or another way to solve this problem (1 Reply)
Discussion started by: murad.jaber
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
we are on RED HAT linux:
$uname -a
Linux myserver.domain.com 2.6.9-42.0.2.ELsmp #1 SMP Thu Aug 17 18:00:32 EDT 2006 i686 i686 i386 GNU/Linux
The only user that can connect in telnet is root. How can I authorize another users to do telnet ?
Many thanks. (1 Reply)
Discussion started by: big123456
1 Replies
4. UNIX for Advanced & Expert Users
Hi all,
I have a problem. I have machine names and their IP addresses in /etc/hosts file. My application does telnet on that machine host name. The application does not uses IP address for tenet. It will fetch the host name from /etc/hosts file.
Now the telnet server runs on customized port.... (6 Replies)
Discussion started by: zing_foru
6 Replies
5. Solaris
Hi,
I need to implement something that will enforce login to a Solaris server as a particular, specifed user. After this login stage, users will be able to "su -" to whichever user they wish, by which time their activity will be captured by some sort of script (yet to be written). What I need... (7 Replies)
Discussion started by: jamiegeo1
7 Replies
6. Solaris
I need to create a user account for a developer that will allow him rwx access to all resources in a directory. How can I do that?
Thanks (5 Replies)
Discussion started by: gsander
5 Replies
7. 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
8. Solaris
Hi all,
I want to create a new user and grant him ONLY transfer files access to a specific directory where he can only upload and read the files. He should be restricted to this activity only.
Regards (6 Replies)
Discussion started by: gilldn
6 Replies
9. AIX
I need to change the security on our AIX servers and disable telnet from all but certain IP addresses.
I have hashed the telnet line in /etc/inetd.conf and added filter rules for those IP adds to allow access on port 23, but this didn't work.
Does anyone have any ideas?
Thanks. (2 Replies)
Discussion started by: Alps
2 Replies
10. UNIX for Advanced & Expert Users
Is there a way to allow a user to use sudo cp on a specific directory and only a specific file? (6 Replies)
Discussion started by: cokedude
6 Replies
TELNETD(8) System Manager's Manual TELNETD(8)
NAME
telnetd - DARPA TELNET protocol server
SYNOPSIS
/usr/libexec/telnetd
DESCRIPTION
Telnetd is a server which supports the DARPA standard TELNET virtual terminal protocol. Telnetd is invoked by the internet server (see
inetd(8)), normally for requests to connect to the TELNET port as indicated by the /etc/services file (see services(5)).
Telnetd operates by allocating a pseudo-terminal device (see pty(4)) for a client, then creating a login process which has the slave side
of the pseudo-terminal as stdin, stdout, and stderr. Telnetd manipulates the master side of the pseudo-terminal, implementing the TELNET
protocol and passing characters between the remote client and the login process.
When a TELNET session is started up, telnetd sends TELNET options to the client side indicating a willingness to do remote echo of charac-
ters, to suppress go ahead, and to receive terminal type information from the remote client. If the remote client is willing, the remote
terminal type is propagated in the environment of the created login process. The pseudo-terminal allocated to the client is configured to
operate in "cooked" mode, and with XTABS and CRMOD enabled (see tty(4)).
Telnetd is willing to do: echo, binary, suppress go ahead, and timing mark. Telnetd is willing to have the remote client do: binary, ter-
minal type, and suppress go ahead.
SEE ALSO
telnet(1C)
BUGS
Some TELNET commands are only partially implemented.
The TELNET protocol allows for the exchange of the number of lines and columns on the user's terminal, but telnetd doesn't make use of
them.
Because of bugs in the original 4.2 BSD telnet(1C), telnetd performs some dubious protocol exchanges to try to discover if the remote
client is, in fact, a 4.2 BSD telnet(1C).
Binary mode has no common interpretation except between similar operating systems (Unix in this case).
The terminal type name received from the remote client is converted to lower case.
The packet interface to the pseudo-terminal (see pty(4)) should be used for more intelligent flushing of input and output queues.
Telnetd never sends TELNET go ahead commands.
4.2 Berkeley Distribution November 16, 1996 TELNETD(8)