From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 23922 invoked from network); 19 Jun 2022 21:16:13 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 19 Jun 2022 21:16:13 -0000 Received: from mail.chrisfroeschl.de ([5.252.227.212]) by 9front; Sun Jun 19 17:14:54 -0400 2022 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chrisfroeschl.de; s=20210522; t=1655673290; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=f95zYvwk7L5lecRyvnIp4vEzyHt/xVMh3LXL2+aEqC0=; b=LJTmU+bjLmrk5A7xzszXaHWQSBf9Y8vIrhjQyjnvx5MVF1qq0ZVsnEo6QY6twNc+E1K7fQ 2gEhfSiwmjznaIfIE5dy5I1u3MbDflE9fSxXryKhGkwY9qF4C1w5K8rBQk/95zX/hmStdd MVP+nMrk8TVmKFxuB0+9CLPEYATaBMI= Received: from cirno.fritz.box ( [82.207.245.22]) by chrisfroeschl.chrisfroeschl.de (OpenSMTPD) with ESMTPSA id a4f4f304 (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO); Sun, 19 Jun 2022 23:14:50 +0200 (CEST) Message-ID: Date: Sun, 19 Jun 2022 23:14:16 +0200 From: chris@chrisfroeschl.de To: 9front@9front.org In-Reply-To: <9d56b04b82722a349b6f453bbe2cad9f.squirrel@mx.sdf.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: service markup CMS CSS reduce/map locator Subject: Re: [9front] ssh: read1: eof when trying to connect to servers Reply-To: 9front@9front.org Precedence: bulk > Whenever I try to ssh into a server, ssh exits with the message > "ssh: read1: eof". I've tried it with -v but I don't see anything that > is an obvious cause. The behavior is the same on multiple servers, > most recently tty.sdf.org? Could it be an issue with secstore or > Factotum? I had the same issue when using ssh for the first time on 9front. You probably have to sysupdate and build the new sources (See 5.2.2 FQA). This contains the most recent version of the ssh client which updates some algorithm logic. For more details see: https://inbox.vuxu.org/9front/CABO6shfqKpXSXYArxfWo8SaWsXKvpjSMFMKdc134AxPCqZrvJA@mail.gmail.com/