From: Arne Fitzenreiter <arne_f@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] OpenSSH: update to 8.2p1
Date: Thu, 09 Apr 2020 18:51:26 +0200 [thread overview]
Message-ID: <15d85ae730243a231b54587964f42d70@ipfire.org> (raw)
In-Reply-To: <3838057a-32cb-8599-6622-bd33c702f528@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
Am 2020-03-24 14:18, schrieb Peter Müller:
> Hello Arne,
>
> to my surprise, OpenSSH 8.2p1 works fine against glibc 2.31, too.
> Password-based
> login is possible in a testing VM using a clean build of the next
> branch with this
> patch applied.
>
> Whatever it was Marcel stumbled across, I cannot reproduce it (or do
> not see it).
>
> In my opinion, this patch can be merged straight away.
But i can reproduce it. OpenSSH 8.2p1 doesn't ask for the credentials
and simple close the connection on i586.
Tested as update and on a new i586 flashimage
I think i have to revert it...
Arne
next prev parent reply other threads:[~2020-04-09 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 20:08 Peter Müller
2020-03-22 9:24 ` Michael Tremer
2020-03-22 15:52 ` Arne Fitzenreiter
2020-03-24 13:18 ` Peter Müller
2020-03-24 14:29 ` Michael Tremer
2020-04-09 16:51 ` Arne Fitzenreiter [this message]
2020-04-09 20:58 ` Michael Tremer
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=15d85ae730243a231b54587964f42d70@ipfire.org \
--to=arne_f@ipfire.org \
--cc=development@lists.ipfire.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