From owner-freebsd-questions Fri Apr 3 12:40:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19598 for freebsd-questions-outgoing; Fri, 3 Apr 1998 12:40:47 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19471 for ; Fri, 3 Apr 1998 12:40:06 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id MAA10884; Fri, 3 Apr 1998 12:40:02 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Fri, 3 Apr 1998 12:40:02 -0800 (PST) From: Doug White Reply-To: Doug White To: Gary Schrock cc: freebsd-questions@FreeBSD.ORG Subject: Re: SIGQUIT in login and ftpd? In-Reply-To: <199804030238.VAA08763@eyelab.psy.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 2 Apr 1998, Gary Schrock wrote: > Any ideas on what might be causing login or ftpd to get SIGQUIT signals? > I've been seeing them periodically on one machine, and can't connect it up > with anything else that looks odd at the time. There used to be a security hole with these (still is?) that SIGQUITting them causes them to coredump, and in the dump is the password file. I don't know if we fixed this or not, or if using login.conf limits we disabled coredumps on normal daemons. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message