From owner-freebsd-security  Sun Apr 28 09:58:33 1996
Return-Path: owner-security
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA10613
          for security-outgoing; Sun, 28 Apr 1996 09:58:33 -0700 (PDT)
Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA10605
          for <security@freebsd.org>; Sun, 28 Apr 1996 09:58:31 -0700 (PDT)
Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with ESMTP id JAA00331; Sun, 28 Apr 1996 09:55:10 -0700 (PDT)
Message-Id: <199604281655.JAA00331@precipice.shockwave.com>
To: "Andrew V. Stesin" <stesin@elvisti.kiev.ua>
cc: firewalls@greatcircle.com, security@freebsd.org
Subject: Re: Q on using "netpipes" for firewall maintanance tasks 
In-reply-to: Your message of "Sun, 28 Apr 1996 17:10:12 +0300."
             <199604281410.RAA21377@office.elvisti.kiev.ua> 
Date: Sun, 28 Apr 1996 09:55:10 -0700
From: Paul Traina <pst@shockwave.com>
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


  From: "Andrew V. Stesin" <stesin@elvisti.kiev.ua>
  Subject: Q on using "netpipes" for firewall maintanance tasks
  Hello people,
  
  I'm now in a search for safer but convenient rsh(1) replacement for some
  tasks of firewall day-to-day operation, i.e. gathering some stats, etc.
  to an inside machine.  Firewall is composed of FreeBeasts (I like
  that spelling of FreeBSD! :)  no fancy black Cisco boxen for filtering
  routers.

...

  So, I'm seriously considering netpipes as a transport -- only a server
  part is on the firewall machine(s), bound to a preselected set
  of ports, with /bin/sh script attached to it.
  
  Where am I wrong?

Not buying the cisco box.