From owner-freebsd-bugs Tue Oct 22 19:33:49 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA24154 for bugs-outgoing; Tue, 22 Oct 1996 19:33:49 -0700 (PDT) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA24143; Tue, 22 Oct 1996 19:33:42 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (8.7.5/8.7.3) with ESMTP id WAA25027; Tue, 22 Oct 1996 22:32:46 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.7.3) with ESMTP id WAA19793; Tue, 22 Oct 1996 22:31:26 -0400 (EDT) To: "Marc G. Fournier" cc: mark@grondar.za, freebsd-bugs@freefall.freebsd.org From: "Gary Palmer" Subject: Re: bin/826 In-reply-to: Your message of "Tue, 22 Oct 1996 14:34:21 PDT." <199610222134.OAA05894@freefall.freebsd.org> Date: Tue, 22 Oct 1996 22:31:25 -0400 Message-ID: <19791.846037885@orion.webspan.net> Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk "Marc G. Fournier" wrote in message ID <199610222134.OAA05894@freefall.freebsd.org>: > Synopsis: tcpmux listener in inetd does not work > > State-Changed-From-To: open-feedback > State-Changed-By: scrappy > State-Changed-When: Tue Oct 22 14:32:08 PDT 1996 > State-Changed-Why: > > This problem seems to still exist...does anyone know anything > about tcpmux? I talked to Garrett about this a while back and never had a chance to look at it again. His point of view is that it should be disabled, code removed, and documented because it's a security hole (makes firewall admin's nervous or somesuch). And a very valid point made by Garrett: There are plenty of unassigned port numbers ... why do we need to mux them? Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info