From owner-freebsd-security Tue Nov 20 9:24:55 2001 Delivered-To: freebsd-security@freebsd.org Received: from sanyu1.sanyutel.com (sanyu1.sanyutel.com [216.250.215.14]) by hub.freebsd.org (Postfix) with ESMTP id F382237B503 for ; Tue, 20 Nov 2001 09:24:48 -0800 (PST) Received: from localhost (ksemat@localhost) by sanyu1.sanyutel.com (8.11.3/) with ESMTP id fAKHPkU28254; Tue, 20 Nov 2001 20:25:46 +0300 X-Authentication-Warning: sanyu1.sanyutel.com: ksemat owned process doing -bs Date: Tue, 20 Nov 2001 20:25:46 +0300 (EAT) From: X-X-Sender: To: Mitch Collinsworth Cc: Carroll Kong , Mike Tancsa , Subject: Re: Fwd: Vendors For WU-FTPD Please Read In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Agreed, a few less is always better than a few more. But applying > security updates is part of our job as sysadmins. If you have lots > of boxen to look after, you need to automate the update process. > There are various approaches to this. I like cfengine. We're now > experimenting with PXE and auto reinstalls. There are other good > approaches besides these. rdist is an interesting approach for keeping multiple machine upto date. on the note about ftp daemons. I hav been using vsftpd for some time and I am yet to hear of any security bugs. I like the simple way in which one can chroot users to their home directories by simply putting the user name in a file. Noah. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message