09-15-2001
Passwords control telnet access.
IP filter rules (in firewalls, etc.) control IP address and port access to services.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We use SCO OSR5 with TermLIte to create telnet sessions.
If you accidently click X on the TermLite screen and exit the session you leave process running. I've heard of a program that will allow you to re-connect to these 'floating' sessions and then be able to carry on your session.
Does anyone... (2 Replies)
Discussion started by: mikeh
2 Replies
2. UNIX for Advanced & Expert Users
Anyone know how to limit the telnet sessions on a per user basis on an HP UX Box.
I would like to limit the Maximum number of telnet seesions a user can open at any give time to around 4 or 5. I have been looking and looking and do not seem to be able to find anything on this. Any help would be... (2 Replies)
Discussion started by: Witlr
2 Replies
3. Linux
Hi,
I want to create a user and allow its to be able to have telnet session like what you have in the ftp allow and deny. Is this possible
Thanx. (3 Replies)
Discussion started by: kayode
3 Replies
4. UNIX for Dummies Questions & Answers
we moved to new server this weekend.
npty nstrpty nstrtel all set to 700
now this AM, users are getting on and after 60 (which was the default for those parms) users - everyone else gets a telnet msg.
I urgently need to know what is causing this and how to fix.
thank you.
Lisa (3 Replies)
Discussion started by: LisaS
3 Replies
5. Solaris
I am trying to find the following information regarding the logging of telnet sessions within a Solaris 10 environment:
(1) How can I tell if the logging of telnet sessions is enabled on a Solaris 10 machine?
(2) Assuming that the logging of telnet sessions is not enabled, what is the... (1 Reply)
Discussion started by: RobSand
1 Replies
6. Red Hat
Hi Users,
Kindly help me with below query of mine.
Using Red Hat Linux Enterprise Edition as the client how many simultaneous
1) Maximum FTP sessions are allowed
2) Maximum Telnet sessions are allowed
3) any special settings need to be enabled for maximum telnet and ftp sessions on... (2 Replies)
Discussion started by: newbie07
2 Replies
7. HP-UX
Currenly my hp-ux server can take the default of 60 telnet connections,
i want to know how i can increase this. and also can i effect such changes without doing a reboot.
My server is HP-UX B.11.23 (1 Reply)
Discussion started by: tomjones
1 Replies
8. Solaris
hello guys, Does anybody know how I can log all the telnet sessions for a specific IP.
For instance, anybody who make a telnet to IP x.x.x.x this session will be logged. the purpose of it is that I need to know every command that people are running on this node.
Any help ?
Thanks. (1 Reply)
Discussion started by: cerioni
1 Replies
9. Solaris
Hi,
My requirement - for security purpose -
I want all root logins to my solaris servers are done by a script kept
in a separate unix box. This script will telnet into remote solaris server with
root user and log every session via log file.
Now my purpose is to log every telnet session... (3 Replies)
Discussion started by: rahul_jain250
3 Replies
10. AIX
Hi
The telnet sessions stay as idle users. It is not getting kicked out.
Please advise what could be the issue. only when we reboot the server these telnet sessions goes.
Below is the current output from the server. we rebooted the server three days ago:
pmut6:/> uptime
04:21PM... (8 Replies)
Discussion started by: newtoaixos
8 Replies
LEARN ABOUT DEBIAN
tcpdchk
TCPDCHK(8) System Manager's Manual TCPDCHK(8)
NAME
tcpdchk - tcp wrapper configuration checker
SYNOPSIS
tcpdchk [-a] [-d] [-i inet_conf] [-v]
DESCRIPTION
tcpdchk examines your tcp wrapper configuration and reports all potential and real problems it can find. The program examines the tcpd
access control files (by default, these are /etc/hosts.allow and /etc/hosts.deny), and compares the entries in these files against entries
in the inetd network configuration file.
tcpdchk reports problems such as non-existent pathnames; services that appear in tcpd access control rules, but are not controlled by tcpd;
services that should not be wrapped; non-existent host names or non-internet address forms; occurrences of host aliases instead of official
host names; hosts with a name/address conflict; inappropriate use of wildcard patterns; inappropriate use of NIS netgroups or references to
non-existent NIS netgroups; references to non-existent options; invalid arguments to options; and so on.
Where possible, tcpdchk provides a helpful suggestion to fix the problem.
OPTIONS
-a Report access control rules that permit access without an explicit ALLOW keyword.
-d Examine hosts.allow and hosts.deny files in the current directory instead of the default ones.
-i inet_conf
Specify this option when tcpdchk is unable to find your inetd.conf network configuration file, or when you suspect that the program
uses the wrong one.
-v Display the contents of each access control rule. Daemon lists, client lists, shell commands and options are shown in a pretty-
printed format; this makes it easier for you to spot any discrepancies between what you want and what the program understands.
FILES
The default locations of the tcpd access control tables are:
/etc/hosts.allow
/etc/hosts.deny
SEE ALSO
tcpdmatch(8), explain what tcpd would do in specific cases.
hosts_access(5), format of the tcpd access control tables.
hosts_options(5), format of the language extensions.
inetd.conf(5), format of the inetd control file.
AUTHORS
Wietse Venema (wietse@wzv.win.tue.nl),
Department of Mathematics and Computing Science,
Eindhoven University of Technology
Den Dolech 2, P.O. Box 513,
5600 MB Eindhoven, The Netherlands
TCPDCHK(8)