I recently had a request from a user as why a web site he was trying to
access was not working properly. I discovered that the site was a medical
information database which had a wierd db engine at the back trying to
output http on another port than 80. When I interrogated the site creator
they replied that the database engine manuf defaulted to that and they were
told it was more secure.

I don't think the site lasted very long!
 
Stuart Ward

        Technical Implementation and Support Executive

        [EMAIL PROTECTED]

        01527 592880  fax 01527 592881

        This message is intended only for the use of the person(s) ("the
intended recipient(s)") to whom it is addressed.
        It may contain information which is privileged and confidential
within the meaning of applicable law.
        If you are not the intended recipient, please contact the sender as
soon as possible.
        The views expressed in this communication may not necessarily be the
views held by PharMed Limited.
 

> -----Original Message-----
> From: Josh Medina [mailto:[EMAIL PROTECTED]]
> Sent: 18 July 2001 02:48
> To: [EMAIL PROTECTED]
> Subject: Re: [FW1] Do you allow http to ports other than 80?
> 
> 
> 
> I certainly would not allow this. I might allow an FTP site 
> on another port,
> but even then I would asign the port and ask a lot questions.
> 
> 
> 
> ----- Original Message -----
> From: "Greg Winkler" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, July 16, 2001 1:34 PM
> Subject: [FW1] Do you allow http to ports other than 80?
> 
> 
> >
> >
> > Recently I've been bombarded by requests from my users to 
> gain access to
> > websites outside the company that run on ports other than 
> 80. Off the top
> > of my head I recall sites running on 9022, 8095, 81, 89, 
> 8081, 8080, and
> > I'm sure I've forgotten a few. Up until today I could never 
> get them to
> > work. I've just learned that, YES, it is possible to allow this on a
> > firewall by creating a new service with a protocol type set 
> to URI and by
> > adding a line to fwauthd.conf of the format
> >
> > port#         in.ahttpd       wait    0
> >
> > It was the update to fwauthd.conf that had me stymied.
> >
> > My only objection now is that each of these new ports 
> requires another
> http
> > security server process to monitor it. I'd just as soon not 
> have a million
> > security servers running on my firewall to support a very 
> small community
> > of users who need access to these oddball websites.
> >
> > Just what is it with these website admins? Why must they 
> run their sites
> on
> > odd port numbers? What's scary is that some of the sites 
> are running on
> > ports that have been assigned to other services. What the 
> heck is one to
> do
> > when the web-site conflicts with the legitimate use of that port?
> >
> > I feel like making a stand...."Just say NO to websites that 
> don't run on
> > port 80". But it appears I will just get stampeded. Do you 
> allow access to
> > these sites where you work?
> >
> > 
> --------------------------------------------------------------
> ------------
> --------------
> >
> > Greg Winkler
> > Systems Manager, IT&S
> > Huntsman Corporation
> > Internet Mail: [EMAIL PROTECTED]
> > Voice: (713) 235-6018
> > Fax: (713) 235-6890
> >
> >
> >
> >
> >
> ==============================================================
> ==============
> ====
> >      To unsubscribe from this mailing list, please see the 
> instructions at
> >                http://www.checkpoint.com/services/mailing.html
> >
> ==============================================================
> ==============
> ====
> >
> >
> 
> 
> 
> ==============================================================
> ==================
>      To unsubscribe from this mailing list, please see the 
> instructions at
>                http://www.checkpoint.com/services/mailing.html
> ==============================================================
> ==================
> 


================================================================================
     To unsubscribe from this mailing list, please see the instructions at
               http://www.checkpoint.com/services/mailing.html
================================================================================

Reply via email to