From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] openssh-8.9_p1 does not accept connections when running on a 32-bit host
Date: Wed, 02 Mar 2022 04:55:43 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35913@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
New issue by amak79 on void-packages repository
https://github.com/void-linux/void-packages/issues/35913
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.10.92_1 armv7l Unknown uptodate rFFFF
* package:
openssh-8.9p1_1
The client (amd64) outputs the following message when attempting a connection:
```
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
Connection reset by 192.168.0.8 port 22
```
The server (armv7l) will log the following:
```
[ 750.684869] audit: type=1326 audit(1646192346.110:2): auid=4294967295 uid=99 gid=99 ses=4294967295 pid=557 comm="sshd" exe="/usr/bin/sshd" sig=31 arch=40000028 syscall=414 compat=0 ip=0x76bbcbd8 code=0x0
```
Applying the patch from the upstream and building openssh locally fixes the issue. Upstream bug: https://bugzilla.mindrot.org/show_bug.cgi?id=3396
next reply other threads:[~2022-03-02 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 3:55 amak79 [this message]
2022-03-03 17:12 ` sshd " ZyxerZyxani
2022-03-03 19:22 ` [ISSUE] [CLOSED] " leahneukirchen
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35913@inbox.vuxu.org \
--to=amak79@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).