9front - general discussion about 9front
 help / color / mirror / Atom feed
From: aeggenberger@sdf.org
To: 9front@9front.org
Subject: Re: [9front] ssh: read1: eof when trying to connect to servers
Date: Tue, 21 Jun 2022 02:30:34 -0500	[thread overview]
Message-ID: <1AE8E6504633E79DFA04C15DB707C503@sdf.org> (raw)
In-Reply-To: <BDC6CC68EA5EE2CA9AED2F6DAD874E9A@chrisfroeschl.de>

Quoth chris@chrisfroeschl.de:

> 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/

Thanks. I tried building and installing everything, but the problem persists.

Here's the output of ssh -d aeggenberger@sdf.org.

term% ssh -d aeggenberger@sdf.org
server version: SSH-2.0-OpenSSH_8.8
kexalgs: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256
hostalgs: rsa-sha2-512,rsa-sha2-256,ssh-ed25519
cipher1: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
cipher2: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
mac1: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
mac2: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
zip1: none,zlib@openssh.com
zip2: none,zlib@openssh.com
ssh: read1: eof

  reply	other threads:[~2022-06-21  2:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-19 15:43 aeggenberger
2022-06-19 15:57 ` ori
2022-06-19 21:14 ` chris
2022-06-21  7:30   ` aeggenberger [this message]
2022-06-21  7:31   ` aeggenberger
2022-06-21  2:35     ` ori
2022-06-21  7:45       ` aeggenberger
2022-06-21  2:48         ` ori
2022-06-21  8:37     ` ng
2022-06-21  8:05 aeggenberger
2022-06-21  5:00 ` ori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1AE8E6504633E79DFA04C15DB707C503@sdf.org \
    --to=aeggenberger@sdf.org \
    --cc=9front@9front.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).