Great Circle Associates Firewalls
(April 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: opening arbitrary ports- bad idea, or acceptable?
From: "Wadzinski, Tom IS" <Tom . Wadzinski @ heitman . com>
Date: Tue, 15 Apr 1997 18:01:07 -0500
To: firewalls @ GreatCircle . COM

Hello,
I have a question about TCP/UDP services not supported by a given
firewall.  When I search for the right firewall for our org, I often ask
vendors about what happens if I have a service that their firewall don't
support.  With most vendors, they'll say, " Simple, create a "rule" that
says, basically: Open port xxx for whatever external(untrusted) sites
you want to be able to communicate with whatever internal(trusted)sites
you want."   They act like this is no big deal, but isnt' this really a
large security risk, just allowing any traffic on a particular port to
pass?


My main goal is to create a fairly secure method of having remote user's
(who are running NT Workstation 4.0, etc..) access an NT domain through
a firewall. If anyone has had success with users using dial-up
networking to login into to an NT domain through a firewall, I would
love to hear about it.  


Tom Wadzinski

Indexed By Date Previous: RE: Firewall-1 on a Pentium - Performance Test Results?
From: Luis Alberto Barraza del Castillo <lbarraza @ infosel . com . mx>
Next: Re: ipfw ruleset
From: Bernd Eckenfels <lists @ lina . inka . de>
Indexed By Thread Previous: Re: encryption exports
From: Bob Beck <beck @ obtuse . com>
Next: opening arbitrary ports- bad idea, or acceptable? -Reply
From: Scott Fagg <scott . fagg @ arup . com>

Google
 
Search Internet Search www.greatcircle.com