Sponsored Content
Full Discussion: Restricting Telnet to IPs
Special Forums Cybersecurity Restricting Telnet to IPs Post 24112 by sansolaris on Friday 5th of July 2002 05:37:07 AM
Old 07-05-2002
blocking telnet

You can block outgoing telnet to a specific host from your machine by blocking data that's going out of your machine to that external host' port 23. If you are using Linux and iptables, you can use this

iptables -A OUTPUT -d <ip-of-blocked-host> --dport 23 -j DENY

If you are using Solaris, then you can do the blocking with ip filter.

-Sanjay
 

10 More Discussions You Might Find Interesting

1. Cybersecurity

restricting access...

restricted access... Hi I need to restrict users shell access to only $HOME under /home for each user. I don't want them getting out of their own directories. From what I understand chroot is something I could use, but I want to avoid this since it involves creating symbolic links to a number... (9 Replies)
Discussion started by: alwayslearningunix
9 Replies

2. UNIX for Dummies Questions & Answers

Restricting access

I need to create a user that only has access to 1 directory (e.g. /vol/mita/test). The user needs to be able to rsh into that directory to run a script. The user should not be able to navigate to any other directories above /vol/mita/test. Any help would be appreciated! (4 Replies)
Discussion started by: ngagne
4 Replies

3. UNIX for Dummies Questions & Answers

Restricting Telnet to IPs

Dear Experts, Is it possible to restrict telnet to specific ips in Digital Unix Thanks (4 Replies)
Discussion started by: geraldwilson
4 Replies

4. Solaris

restricting access

Hi All, I'm on Solaris 8, I need to provide Read-only access to a user to 2 directories only. Using rsh (restricted shell) as the user's login shell, I can restrict the user's access to a certain directory only, but how can I set in such a way that the user can access only the 2 directories... (4 Replies)
Discussion started by: max_min
4 Replies

5. Shell Programming and Scripting

Webpage to Telnet via Perl and Expect: Telnet problem?

Somewhat long story: I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage. This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
Discussion started by: jondo
1 Replies

6. Linux

Restricting IPs on Linux?

I have a need to allow only certain IP addresses to access a machine running Linux. I don't know how would i do it, not an expert at CMD? Thanks in advance for your help. (2 Replies)
Discussion started by: waqaslone
2 Replies

7. UNIX for Dummies Questions & Answers

Automatically login in the telnet from present telnet

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

8. Shell Programming and Scripting

restricting users

how can i make my users to not use particular commands in the network like:wall....... pl z help me regarding this (1 Reply)
Discussion started by: yashwanthguru
1 Replies

9. UNIX for Dummies Questions & Answers

Difference Between Krb5-telnet And Ekrb5-telnet

Hi, I want to know the difference between these two services. Both are under xinetd. Both are used for enabling and disabling Telnet service. So, can somebody please explain me the difference between the two ? Thanks in advance :) (0 Replies)
Discussion started by: kashifsd17
0 Replies

10. Solaris

Restricting use of su - (Solaris 11)

OK. So I can prevent remote systems from logging in as root by uncommenting the CONSOLE entry /etc/default/login. BUT, is there a way to stop su - (when already logged in as own user)? The way we do it is to set up sudoers so users who need access can do sudo su - (2 Replies)
Discussion started by: psychocandy
2 Replies
JDRESOLVE(1)						User Contributed Perl Documentation					      JDRESOLVE(1)

NAME
jdresolve - resolves IP addresses into hostnames SYNOPSIS
jdresolve [-h] [-v] [-n] [-r] [-a] [-d <level>] [-m <mask>] [-l <line cache>] [-t <timeout>] [-p] [-s <number of sockets>] [--database=<db path>] <LOG FILE> jdresolve [--help] [--version] [--nostats] [--recursive] [--anywhere] [--debug=<level>] [--mask=<mask>] [--linecache=<line cache>] [--timeout=<timeout>] [--sockets=<number of sockets>] [--database=<db path>] [--dbfirst] [--dbonly] [--dumpdb] [--mergedb] [--expiredb=<hours>] [--unresolved] [--progress] <LOG FILE> DESCRIPTION
jdresolve resolves IP addresses to hostnames. Any file format is supported, including those where the line does not begin with the IP address. One of the strongest features of the program is the support for recursion, which can drastically reduce the number of unresolved hosts by faking a hostname based on the network that the IP belongs to. DNS queries are sent in parallel, which means that you can decrease run time by increasing the number of simultaneous sockets used (given a fast enough machine and available bandwidth ). By using the database support, performance can be increased even further, by using cached data from previous runs. OPTIONS
-h, --help produces a short help message -v, --version display version information -n, --nostats don't display stats after processing -r, --recursive recurse into C, B and A classes when there is no PTR (default is no recursion) -d, --debug=<debug-level> debug mode - no file output, just statistics during run (verbosity level range: 1-3) -t, --timeout=<seconds> timeout in seconds for each host resolution (default is 30 seconds) -l, --line-cache=<lines> numbers of lines to cache in memory (default is 10000 -s, --sockets=<sockets> maximum number of concurrent sockets (use ulimit -a to check the max allowed for your operating system - defaults to 64) -m, --mask=<mask> <mask> accepts %i for IP and %c for class owner, e.g. "somewhere.in.%c" or "%i.in.%c" (default is "%i.%c") -a, --anywhere resolves IPs found anywhere on a line (will resolve all IPs if there is more than one) -p, --progress prints a nice progress bar indicating the status of the resolve operations --database=<db path> path to database that holds resolved hosts/classes --dbfirst check if we have resolved entries in the database before sending out DNS queries --dbonly don't send DNS queries, use only resolved data in the database --dumpdb dumps a database to STDOUT --mergedb merges resolved IP/classes from a file (or STDIN) with a database --expiredb=<hours> expires entries in the database that are older than <hours> hours --unresolved won't attempt to resolve IPs, only lists those that were not resolved <LOG FILE> the log filename or '-' for STDIN EXAMPLES
jdresolve access_log > resolved_log jdresolve -r -s 128 access_log > resolved_log jdresolve -r --database hosts.db access_log > res_log SEE ALSO
rhost(1) AUTHOR
jdresolve was written by John D. Rowell <me@jdrowell.com>, and is licensed under the terms of the GNU General Public License. The original version of this man page was written by Craig Sanders <cas@taz.net.au>, for the Debian GNU/Linux package of jdresolve, and is also licensed under the terms of the GNU GPL. 3rd Berkeley Distribution perl 5.005, patch 03 JDRESOLVE(1)
All times are GMT -4. The time now is 09:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy