From: Sam James <sam@gentoo.org>
To: distributions@lists.linux.dev
Subject: OpenSSL 3.1.0 and OpenSSH
Date: Wed, 15 Mar 2023 04:16:49 +0000 [thread overview]
Message-ID: <87lejy7ilz.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
Hi folks,
OpenSSH currently has an overly restrict version check
for the runtime OpenSSL version vs the built-against-version,
so if you upgrade from e.g. openssl 3.0.x -> openssl 3.1.x
without rebuilding openssh (and you shouldn't need to, as
3.1.x is ABI compatible with 3.0.x), you'll get:
```
$ ssh -V
OpenSSL version mismatch. Built against 30000080, you have 30100000
```
I've reported a bug upstream and they're already on it, but
an FYI to avoid breaking your (or possibly other peoples' ;))
systems.
Upstream bug is https://bugzilla.mindrot.org/show_bug.cgi?id=3548.
best,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
reply other threads:[~2023-03-15 4:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87lejy7ilz.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=distributions@lists.linux.dev \
/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