10-30-2008
Are ports above 1024 closed by default ?
Hi guys,
Just needed to know if all the ports above 1024 are closed by default. I know that below 1024 the ports are reserved for the kernel and ports above 1024 are reserved for user applications.
But by default, if I do not have a rule in my firewall to block ports above 1024, Will my system accept incoming or outgoing traffic?. (I think outgoing YES).
I am running CentOS 4.x
Thanks for reading !!
8 More Discussions You Might Find Interesting
1. Cybersecurity
I need to set up an application to run in a script which will be running as a web server but is a database. I need to allow users to use the web server but the app must be run as root in order for the ports to be accessible. This is not a very secure environment would like to know how this could... (2 Replies)
Discussion started by: rpollard
2 Replies
2. UNIX for Dummies Questions & Answers
Hello
I need to close some ports on a box Solaris 8, which command I need to use.
Thanks for your replies (2 Replies)
Discussion started by: lo-lp-kl
2 Replies
3. UNIX for Dummies Questions & Answers
Hi Everyone,
Good day.
Scenario:
2 unix servers -- A (SunOS) and B (AIX)
I have an ftp script to sftp 30 files from A to B which happen almost instantaneously i.e 30 sftp's happen at the same time.
Some of these sftp's fail with the following error:
ssh_exchange_identification: Connection... (1 Reply)
Discussion started by: jeevan_fimare
1 Replies
4. Red Hat
Hi All,
How do I know if ssh_host_rsa_key is 1024 bit?
cat /etc/ssh/ssh_host_rsa_key | wc -m
887
It's only 887. Is that it? Or not?
Thank you for any comment you may add. (2 Replies)
Discussion started by: itik
2 Replies
5. UNIX for Dummies Questions & Answers
How to generate RSA 1024 public key??
Pls help (3 Replies)
Discussion started by: kdtrica
3 Replies
6. Shell Programming and Scripting
Hi i have a txt file in which i do a awk operation with ":" as field separator
A
B
C
D
ABC::2386.13:2386.13:3248234281995::+DPY:INT:3:N::::2:200.00:0.00:2010-05-12:CA:
::2:N::N:PH:00010031:0001+DPY:BAL:3:N::::3:1601.01:0.00:2010-05-12:XT::2:N:MR ... (1 Reply)
Discussion started by: mad_man12
1 Replies
7. Solaris
Dear all,
I have a Solaris 10 system with a bunch of zones on it. My issue is the following:
- I have application A and B running in the same zone: i.e. they communicate via loopback interface. Application A tries to connect to application B, usually listening on port X. If application B... (6 Replies)
Discussion started by: pierolinux
6 Replies
8. IP Networking
Hey guys, I'm having trouble with checking what ports are open on my Debian distro, which is reporting all ports closed, though they are clearly open
I am checking to see if ports are open with netcat:
nc 127.0.0.1 80
localhost 80 (http) : Connection refusedAs an example but on all ports... (0 Replies)
Discussion started by: 3therk1ll
0 Replies
LEARN ABOUT CENTOS
aconnect
aconnect(1) General Commands Manual aconnect(1)
NAME
aconnect - ALSA sequencer connection manager
SYNOPSIS
aconnect [-d] [-options] sender receiver
aconnect -i|-o [-options]
aconnect -x
DESCRIPTION
aconnect is a utility to connect and disconnect two existing ports on ALSA sequencer system. The ports with the arbitrary subscription
permission, such as created by aseqview(1), can be connected to any (MIDI) device ports using aconnect. For example, to connect from port
64:0 to 65:0, run as follows:
% aconnect 64:0 65:0
The connection is one-way, and the whole data to the sender port (64:0) is redirected to the receiver port (65:0). When another port (e.g.
65:1) is attached to the same sender port, the data is sent to both receiver ports. For disconnection, use -d option.
% aconnect -d 64:0 65:0
The address can be given using the client's name.
% aconnect External:0 Emu8000:1
Then the port 0 of the client matching with the string "External" is connected to the port 1 of the client matching with the "Emu8000".
Another function of aconnect is to list the present ports on the given condition. The input ports, which may become sender ports, can be
listed with -i option.
% aconnect -i
client 0: 'System' [type=kernel]
0 'Timer '
1 'Announce '
client 64: 'External MIDI-0' [type=kernel]
0 'MIDI 0-0 '
Similarly, to see the output ports, use -o flag.
You can remove all existing exported connections using -x option. This function is useful for terminating the ALSA drivers, because the
modules with sequencer connections cannot be unloaded unless their connections are removed.
OPTIONS
CONNECTION MANAGEMENT
-d, --disconnect
Disconnect the given subscription.
-e, --exclusive
Connect ports with exclusive mode. Both sender and receiver ports can be no longer connected by any other ports.
-r, --real queue
Convert time-stamps of event packets to the current value of the given real-time queue. This is option is, however, not so useful,
since the receiver port must use (not necessarily own) the specified queue.
-t, --tick queue
Like -r option, but time-stamps are converted to the current value of the given tick queue.
LIST PORTS
-i, --input
List existing input (readable) ports. This option is exclusive to -o.
-o, --output
List existing output (writable) ports. This option is exclusive to -i.
-l, --list
List the current connection status. The connected and connecting ports from/to each port are listed together. The suffix flag [ex]
means the connection is exclusive. The suffix flag [real:#] and [tick:#] mean the connection includes real-time and tick conversion
on the listed queue, respectively.
REMOVE ALL CONNECTIONS
-x, --removeall
Remove all exported connections.
SEE ALSO
aseqnet(1), aseqview(1)
AUTHOR
Takashi Iwai <tiwai@suse.de>
August 31, 2000 aconnect(1)