firewall vs. closing ports


 
Thread Tools Search this Thread
Special Forums Cybersecurity firewall vs. closing ports
# 8  
Old 02-24-2002
Great suggestions by everyone. While we are on this topic ...

You did not mention if this was personal or work use. If you dont have a machine to spare, and don't plan on a firewall or are working on a long term firewall solution, the least that you should do, is to disable access to stuff like telnet, ftp, etc. Telnet, ftp is not secure since you are transmitting cleartext passwords over the internet.

In FreeBSD you can edit the /etc/hosts.allow file to turn off access to some or all of these services. For example, if you absolutely need telnet, then allow it from all the known domains and IPs.

Also check your /etc/services file to see if you can completely turn off some of them.

LivingFree points this appropriately, if you don't have ports open, you can't attack them!
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

Closing thread

Hi, I guess, users do not have rights to close a thread. Please close thread 'Small automation' as it is resolved. Regards, snjksh (1 Reply)
Discussion started by: snjksh
1 Replies

2. UNIX for Dummies Questions & Answers

I have firewall rules to open ports, why telnet refuses connection?

Alright... this question comes from the fact that I'm trying to setup postfix to relay messages to Office 365 SMTP but its giving me connection refused... I read that if you have doubts if your port is open or not you should telnet to them so thats what I did. This is a Red Hat 6.3 box. My... (4 Replies)
Discussion started by: RedSpyder
4 Replies

3. What is on Your Mind?

AllTheWeb closing

It was officially announced that AllTheWeb is closing. Yahoo! no longer supports the function as per april 2011: AlltheWeb.com Before the world turned to google by default, there used to be a plethora of search engines. Most of them gave a headache with the prolific use of colors and animated gifs... (4 Replies)
Discussion started by: figaro
4 Replies

4. Shell Programming and Scripting

closing unwanted open ports using scripts

i have a text file i.e file1.txt which shows open ports on particular system. i have another text file i.e file2.txt which shows a list of allowed ports on a system. for eg: file2.txt 22/tcp ssh 23/tcp telnet. can i have a script which would compare these text files ,file1 and file2 ... (1 Reply)
Discussion started by: anand121
1 Replies

5. Shell Programming and Scripting

closing windows

Ok i know to open a window from a script (mac); open whatever(name of a directory) but i don't how to close it. please some help. thanks. (0 Replies)
Discussion started by: Tártaro
0 Replies

6. Cybersecurity

Firewall Ports

Could someone please settle an inter-office argument? Will your network traffic be slower through a firewall on any other port other than port 80. In other words, is port 80 faster than any other port you open on the firewall. I say no. Thanks in advance for the help! (2 Replies)
Discussion started by: cocolsmith
2 Replies

7. Post Here to Contact Site Administrators and Moderators

Closing a thread

hi, Just wondering if there could be a way to close threads whose creator has got the desired reply. however if someone still wants to give a remark or suggest further on the thread one can still do so. Besides on the control panel there should be some kind of selection criteria to view... (3 Replies)
Discussion started by: linuxpenguin
3 Replies

8. IP Networking

Closing out ports???

Hi all Is there a command that I can use to close out open ports? I did a netstat - a -p and got a long list of ports open (see sample below). I have disabled the some of the applications from /etc/services/. But there are still applications listening on certain ports. I need to know how to... (6 Replies)
Discussion started by: skotapal
6 Replies

9. Cybersecurity

closing open ports

/* Linux Slackware */ Nmap shows the following ports open on the gateway. 21/tcp ftp 22/tcp ssh 23/tcp telnet 25/tcp smtp 37/tcp time 80/tcp http 113/tcp auth 515/tcp printer 587/tcp submission 1024/tcp kdm 6000/tcp x11 ------------------------------- i would like to close as... (10 Replies)
Discussion started by: LowOrderBit
10 Replies
Login or Register to Ask a Question
RDS-PING(1)						    BSD General Commands Manual 					       RDS-PING(1)

NAME
rds-ping -- test reachability of remote node over RDS SYNOPSIS
rds-ping [-c count] [-i interval] [-I local_addr] remote_addr DESCRIPTION
rds-ping is used to test whether a remote node is reachable over RDS. Its interface is designed to operate pretty much the standard ping(8) utility, even though the way it works is pretty different. rds-ping opens several RDS sockets and sends packets to port 0 on the indicated host. This is a special port number to which no socket is bound; instead, the kernel processes incoming packets and responds to them. OPTIONS
The following options are available for use on the command line: -c count Causes rds-ping to exit after sending (and receiving) the specified number of packets. -I address By default, rds-ping will pick the local source address for the RDS socket based on routing information for the destination address (i.e. if packets to the given destination would be routed through interface ib0, then it will use the IP address of ib0 as source address). Using the -I option, you can override this choice. -i timeout By default, rds-ping will wait for one second between sending packets. Use this option to specified a different interval. The timeout value is given in seconds, and can be a floating point number. Optionally, append msec or usec to specify a timeout in milliseconds or microseconds, respectively. Specifying a timeout considerably smaller than the packet round-trip time will produce unexpected results. AUTHORS
rds-ping was written by Olaf Kirch <olaf.kirch@oracle.com>. SEE ALSO
rds(7), rds-info(1), rds-stress(1). BSD
Apr 22, 2008 BSD