Re: Witango-Talk: Blocking Ports ?????????
Blocking that port is fine. As long as you do not have any of your servers on the other side of the router which I doubt you would since it would be pretty hard to hook em up out there without a router :-) We are going to start blocking incoming traffic on the serial interface on our router to tighten up security. We are going to deny all traffic that does not relate to the following ports: pop3, smtp, http, 443, exchange, citrix, dns, and ftp. I know Witango uses port 14100 for something. But is that for internal traffic on the server? Is there anything that flows back and forth to the client browser? Thanks, Steve Fogelson Internet Commerce Solutions TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf -- TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
RE: Witango-Talk: Blocking Ports ?????????
The only port that Witango uses, typically 18100, is used between the CGI or DLL (Web server plugin) and the Witango Daemon (service) itself. In most cases, the web server and the Witango server are the same machine and you simply use the loopback 127.0.0.1, thus a packet never actually leaves or enters the server on that port. If you have a very unique configuration where the router sits between the web server and the Witango server, then you will have to worry about this traffic. Robert -Original Message- From: Fogelson, Steve [mailto:[EMAIL PROTECTED] Sent: Thursday, April 15, 2004 4:34 PM To: Witango User Group (E-mail) Subject: Witango-Talk: Blocking Ports ? We are going to start blocking incoming traffic on the serial interface on our router to tighten up security. We are going to deny all traffic that does not relate to the following ports: pop3, smtp, http, 443, exchange, citrix, dns, and ftp. I know Witango uses port 14100 for something. But is that for internal traffic on the server? Is there anything that flows back and forth to the client browser? Thanks, Steve Fogelson Internet Commerce Solutions TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
RE: Witango-Talk: Blocking Ports ?????????
Thanks for the responses. Witango is on the same server as the web server. Everything is behind the router. And I'm not using SQL. So it looks like I am covered. Thanks Steve -Original Message- From: Robert Shubert [mailto:[EMAIL PROTECTED] Sent: Thursday, April 15, 2004 4:05 PM To: [EMAIL PROTECTED] Subject: RE: Witango-Talk: Blocking Ports ? The only port that Witango uses, typically 18100, is used between the CGI or DLL (Web server plugin) and the Witango Daemon (service) itself. In most cases, the web server and the Witango server are the same machine and you simply use the loopback 127.0.0.1, thus a packet never actually leaves or enters the server on that port. If you have a very unique configuration where the router sits between the web server and the Witango server, then you will have to worry about this traffic. Robert -Original Message- From: Fogelson, Steve [mailto:[EMAIL PROTECTED] Sent: Thursday, April 15, 2004 4:34 PM To: Witango User Group (E-mail) Subject: Witango-Talk: Blocking Ports ? We are going to start blocking incoming traffic on the serial interface on our router to tighten up security. We are going to deny all traffic that does not relate to the following ports: pop3, smtp, http, 443, exchange, citrix, dns, and ftp. I know Witango uses port 14100 for something. But is that for internal traffic on the server? Is there anything that flows back and forth to the client browser? Thanks, Steve Fogelson Internet Commerce Solutions TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
