From owner-freebsd-security Thu Mar 22 13:12:36 2001 Delivered-To: freebsd-security@freebsd.org Received: from theshell.com (arsenic.theshell.com [63.236.138.5]) by hub.freebsd.org (Postfix) with SMTP id AAECB37B718 for ; Thu, 22 Mar 2001 13:12:30 -0800 (PST) (envelope-from pavalos@theshell.com) Received: (qmail 8935 invoked from network); 22 Mar 2001 21:12:31 -0000 Received: from arsenic.theshell.com (HELO tequila) (root@63.236.138.5) by arsenic.theshell.com with SMTP; 22 Mar 2001 21:12:31 -0000 From: "Peter Avalos" To: Subject: RE: Multiple vendors FTP denial of service Date: Thu, 22 Mar 2001 15:14:53 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20010317174640.F20830@speedy.gsinet> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The reality that only a select few daemons use /etc/login.conf > > is admittedly counter-intuitive. Perhaps this is more of a job Does cron use login.conf? > Until there's an aggreed upon and clean solution, would a comment > at the top of /etc/login.conf raise attention? Maybe with If cron does use login.conf, how about a short statement in the man page about it? --Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message