From owner-freebsd-security  Mon Jul 28 11:32:39 1997
Return-Path: <owner-freebsd-security>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA23304
          for security-outgoing; Mon, 28 Jul 1997 11:32:39 -0700 (PDT)
Received: from mail.MCESTATE.COM (vince@mail.MCESTATE.COM [207.211.200.50])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA23293
          for <security@FreeBSD.ORG>; Mon, 28 Jul 1997 11:32:34 -0700 (PDT)
Received: from localhost (vince@localhost)
	by mail.MCESTATE.COM (8.8.5/8.8.5) with SMTP id LAA05287;
	Mon, 28 Jul 1997 11:31:55 -0700 (PDT)
Date: Mon, 28 Jul 1997 11:31:55 -0700 (PDT)
From: Vincent Poy <vince@mail.MCESTATE.COM>
To: Robert Watson <robert@cyrus.watson.org>
cc: Guido van Rooij <guido@gvr.win.tue.nl>, loco@onyks.wszib.poznan.pl,
        security@FreeBSD.ORG, mario1@PrimeNet.Com, johnnyu@accessus.net
Subject: Re: security hole in FreeBSD
In-Reply-To: <Pine.BSF.3.95q.970728105715.3000H-100000@cyrus.watson.org>
Message-ID: <Pine.BSF.3.95.970728113012.3844P-100000@mail.MCESTATE.COM>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-security@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 28 Jul 1997, Robert Watson wrote:

=)> > BTW, does anyone know if there is a secure logging protocol?  Syslog on
=)> > UDP seems a tad unreliable, not to mention opening one up from DoS.  I log
=)> 
=)> Not on local delivery of udp packets. Nowadays, the FreeBSD syslogd is shipped
=)> with an option -s that makes it refuse syslog messages form remote
=)> machins. This of course does not help if you want to be able to get
=)> syslog entries from a remote host. But you can refure udp packet
=)> with destination port 513 on your routers.
=)
=)Unfortunately, I don't have the liberty of reconfiguring some of the
=)routers my hosts are acessible through.  Using ipfirewall to restrict
=)incoming messages is possible, but undesirable as it doesn't help against
=)spoofing, if the threat is also inside your network.  The vulnerable host
=)in the -s case is the loghost, which must accept network log messages.
=)Configuring with a default of -s is a good arrangement.

	What does the -s do anyways?  I know it means secure but isn't it
supposed to be secure already out of the box?


Cheers,
Vince - vince@MCESTATE.COM - vince@GAIANET.NET           ________   __ ____ 
Unix Networking Operations - FreeBSD-Real Unix for Free / / / / |  / |[__  ]
GaiaNet Corporation - M & C Estate                     / / / /  | /  | __] ]  
Beverly Hills, California USA 90210                   / / / / / |/ / | __] ]
HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____]