From owner-freebsd-questions@FreeBSD.ORG Fri May 11 14:59:22 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA2EE16A416 for ; Fri, 11 May 2007 14:59:22 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail3.sea5.speakeasy.net (mail3.sea5.speakeasy.net [69.17.117.5]) by mx1.freebsd.org (Postfix) with ESMTP id 973E913C4B9 for ; Fri, 11 May 2007 14:59:22 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 32419 invoked from network); 11 May 2007 14:59:22 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail3.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 11 May 2007 14:59:21 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 12B852842D; Fri, 11 May 2007 10:59:19 -0400 (EDT) To: freebsd-questions@freebsd.org References: <20070509224851.GY25685@rescomp.berkeley.edu> From: Lowell Gilbert Date: Fri, 11 May 2007 10:59:19 -0400 In-Reply-To: <20070509224851.GY25685@rescomp.berkeley.edu> (Christopher Cowart's message of "Wed\, 9 May 2007 15\:48\:51 -0700") Message-ID: <44ejln4da0.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.99 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: sshd segfaults on exit when no tty allocated X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2007 14:59:22 -0000 Christopher Cowart writes: > When I ssh into FreeBSD hosts without allocating a tty, sshd segfaults > after the process terminates. This problem occurs on both 6_1_REL and > 6_2_REL installations at all sorts of patch levels. > > Examples: > > Client: `ssh -t server ls` > Server Logs: > | May 9 15:33:44 server sshd[1503]: Accepted publickey for ccowart from > | client port 43604 ssh2 > | May 9 15:33:45 server sshd[1505]: pam_sm_close_session(): no utmp > | record for ttyp5 > > Client: `ssh server ls` > Server Logs: > | May 9 15:33:50 server sshd[1509]: Accepted publickey for ccowart from > | client port 42119 ssh2 > | May 9 15:33:51 server pid 1511 (sshd), uid 1225: exited on signal 11 > > In either example, the client thinks the command has completed > successfully, shows proper output, and propogates the return value from > the remote command. The main problem is I don't like seeing a bunch of > segfaults being logged in the daily run output. > > Our sshd_config stock, except we set `PermitRootLogin yes`. > > Does anyone know why this happens? Should I file a problem report? I can't reproduce it on my own machines (-STABLE, a few weeks old), so a PR probably would need a more precise reproduction scenario.