Its generally a good idea only to open ports that necesarry (eg. 80 for
http, 21 for ftp, etc..). Opening up unnecesarry ports and/or running
unnecesarry services just opens your server up to security vulnerabilities.
In your case I don't really understand what you're trying to do. For a web
In my case, a third-party application requires port TCP 100 open. I used a
conduit from the PIX allowing in/outbound traffic to that specific server IP
address where the application resides.
My question is, how can I make sure this TCP 100 port is going to be secure
as possible... I would like
Don Nguyen wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Its generally a good idea only to open ports that necesarry (eg. 80 for
http, 21 for ftp, etc..). Opening up unnecesarry ports and/or running
unnecesarry services just opens your server up to security
vulnerabilities.
- opening ports other than 80 and [7:42333]
Don Nguyen wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Its generally a good idea only to open ports that necesarry (eg. 80
for http, 21 for ftp, etc..). Opening up unnecesarry ports and/or
running unnecesarry services ju
Thanks
Larry
-Original Message-
From: nrf [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 23, 2002 1:57 PM
To: [EMAIL PROTECTED]
Subject: Re: Security advice - opening ports other than 80 and [7:42333]
Don Nguyen wrote in message
[EMAIL PROTECTED]">news:[EMAIL PRO
5 matches
Mail list logo