From owner-freebsd-hackers Sun Jul 20 10:06:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA24533 for hackers-outgoing; Sun, 20 Jul 1997 10:06:30 -0700 (PDT) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA24501 for ; Sun, 20 Jul 1997 10:06:18 -0700 (PDT) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.6.11/8.6.10) with SMTP id UAA06014; Sun, 20 Jul 1997 20:06:00 +0300 X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Sun, 20 Jul 1997 20:06:00 +0300 (IDT) From: Nadav Eiron X-Sender: nadav@csd To: Wilko Bulte cc: FreeBSD hackers list Subject: Re: ipfw and secure http In-Reply-To: <199707201526.RAA02191@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 20 Jul 1997, Wilko Bulte wrote: > Quick question: I just had a little collision with ipfw (due to me..). > I tried to access a server that uses secure http (is that the right > name for it anyway?). In any case it wanted to access the port# > corresponding to https (instead of http). > > Am Icorrect in assuming the packetfiltering characteristics are identical > to http save for the https port# ? Yes, and both can easily be served by a proxy too, which is generally considered safer than letting the packets through. Anyhow, you should be fine just letting them through with ipfw. The port number is 443, BTW. > > Wilko > _ ____________________________________________________________________ > | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, TheNetherlands > |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda > -------------------------------------------------------------------------- > Nadav