From owner-freebsd-arm@FreeBSD.ORG Sun Sep 15 06:27:41 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 67831D60 for ; Sun, 15 Sep 2013 06:27:41 +0000 (UTC) (envelope-from paradyse@gmail.com) Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0748920DF for ; Sun, 15 Sep 2013 06:27:40 +0000 (UTC) Received: by mail-wi0-f178.google.com with SMTP id hn9so2267005wib.17 for ; Sat, 14 Sep 2013 23:27:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=MiobucnmsmLvfNP71TD21EHBP7d7y2bAi6t5ktKLmhI=; b=D1Z7C/v9l0XyMu0ilHXJsGDq91/k5jfGSZT0pKMCFbBoPT83r6xSKbsozqMl9O/uil anDTxSguWEKUZWMs4yDl2Rgg5unG6T52pnaKuI6ocdvBf1zAT3tizz6WGqcyfMHgL6fS rF/VSA3O2hz9V7S/lCzXilVPADLVIw0Yry2Z0tt0fMiPph+W7Xz8bH6v/aYX6hVsLra4 8W/laC42DHtgUQC5D5ZMO7dwGF/LXCMdF2nfS+6PeB0rDdKzt6qRQnBK7pcVE+UmvaMC fCb0u+YOFl+HwQfRBJD7MDV+TrJ6cLWKq5hLHf95T7zcaWPvO3OCdrxd0RiKPfk9o0Vy AJzA== X-Received: by 10.180.205.236 with SMTP id lj12mr8670277wic.22.1379226459328; Sat, 14 Sep 2013 23:27:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.134.170 with HTTP; Sat, 14 Sep 2013 23:27:09 -0700 (PDT) In-Reply-To: References: From: Su Kang Yin Date: Sun, 15 Sep 2013 14:27:09 +0800 Message-ID: Subject: Re: sshd isnt working? To: freebsd-arm Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Sep 2013 06:27:41 -0000 Its totally wierd. Adding "UsePrivilegeSeparation no" in sshd_config work-around it. On 15 September 2013 13:39, Su Kang Yin wrote: > Hi, > > sshd throwing signal 6 on server side > > messages log: > Sep 15 05:32:31 beaglebone kernel: pid 896 (sshd), uid 22: exited on signal 6 > > On FreeBSD version: > FreeBSD beaglebone 10.0-ALPHA1 FreeBSD 10.0-ALPHA1 #0 r255586: Sun Sep > 15 12:53:16 HKT 2013 > root@freebsd:/usr/home/cantona/crochet-freebsd/work/obj/arm.a > rmv6/usr/src.head/sys/BEAGLEBONE arm > > > On the source side of the ssh connection I get this error messages > with verbose mode: > OpenSSH_5.9p1, OpenSSL 0.9.8y 5 Feb 2013 > debug1: Reading configuration data /etc/ssh_config > debug1: /etc/ssh_config line 20: Applying options for * > debug1: /etc/ssh_config line 53: Applying options for * > debug1: Connecting to 192.168.2.2 [192.168.2.2] port 22. > debug1: Connection established. > debug1: identity file /Users/cantona/.ssh/id_rsa type 1 > debug1: identity file /Users/cantona/.ssh/id_rsa-cert type -1 > debug1: identity file /Users/cantona/.ssh/id_dsa type -1 > debug1: identity file /Users/cantona/.ssh/id_dsa-cert type -1 > debug1: Remote protocol version 2.0, remote software version > OpenSSH_6.2_hpn13v11 FreeBSD-20130515 > debug1: match: OpenSSH_6.2_hpn13v11 FreeBSD-20130515 pat OpenSSH* > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_5.9 > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug1: kex: server->client aes128-ctr hmac-md5 none > debug1: kex: client->server aes128-ctr hmac-md5 none > debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent > debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP > debug1: SSH2_MSG_KEX_DH_GEX_INIT sent > debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY > Connection closed by 192.168.2.2 > > Anyone have an idea about this problem? > > Thanks, > Yin