From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] ssh: read1: eof when trying to connect to servers
Date: Sun, 19 Jun 2022 11:57:43 -0400 [thread overview]
Message-ID: <52F73CF674CFF599B0304F575D505466@eigenstate.org> (raw)
In-Reply-To: <9d56b04b82722a349b6f453bbe2cad9f.squirrel@mx.sdf.org>
Quoth aeggenberger@sdf.org:
> 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?
>
you want '-d', not '-v', and you want to paste it so that someone
else can see what could be a cause.
it could be factotum containing the wrong keys, but without seeing
the output I have no idea.
next prev parent reply other threads:[~2022-06-19 15:58 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 [this message]
2022-06-19 21:14 ` chris
2022-06-21 7:30 ` aeggenberger
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F73CF674CFF599B0304F575D505466@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).