On 2/16/20 8:11 PM, Gaetan Bisson wrote:
> [2020-02-16 20:03:16 -0500] Eli Schwartz via arch-dev-public:
>> It's pretty plausible that this commit is simply incompatible with the
>> previous version of sshd, therefore it could not reexec:
>> https://github.com/openssh/openssh-portable/commit/c2bd7f
[2020-02-16 20:03:16 -0500] Eli Schwartz via arch-dev-public:
> It's pretty plausible that this commit is simply incompatible with the
> previous version of sshd, therefore it could not reexec:
> https://github.com/openssh/openssh-portable/commit/c2bd7f74b0e0f3a3ee9d19ac549e6ba89013abaf
>
> So thi
On 2/16/20 7:54 PM, Gaetan Bisson wrote:
>> Is it sufficient to add a post_upgrade message?
>
> Probably, yes but then we'd need a new package out of [testing] fast.
> And users might complain that the post_upgrade message wasn't visible
> enough... :)
We could even try to detect a running sshd.s
On 2/16/20 7:47 PM, Gaetan Bisson via arch-dev-public wrote:
> And I also regret not being able to diagnose what the exact problem is
> just now.
As was pointed out in the bug:
https://bugs.archlinux.org/task/65517#comment186483
ssh errors with:
kex_exchange_identification: read: Connection reset
[2020-02-16 19:53:53 -0500] Santiago Torres-Arias via arch-dev-public:
> On Sun, Feb 16, 2020 at 07:51:19PM -0500, Eli Schwartz via arch-dev-public
> wrote:
> > On 2/16/20 7:47 PM, Gaetan Bisson via arch-dev-public wrote:
> > > Dear all,
> > >
> > > I'd like to post the following news item within
[2020-02-16 19:51:19 -0500] Eli Schwartz via arch-dev-public:
> On 2/16/20 7:47 PM, Gaetan Bisson via arch-dev-public wrote:
> > Dear all,
> >
> > I'd like to post the following news item within the hour.
> >
> >
> >
> > Title: sshd needs restarting after upgrading to openssh-8.2p1
> >
On Sun, Feb 16, 2020 at 07:51:19PM -0500, Eli Schwartz via arch-dev-public
wrote:
> On 2/16/20 7:47 PM, Gaetan Bisson via arch-dev-public wrote:
> > Dear all,
> >
> > I'd like to post the following news item within the hour.
> >
> >
> >
> > Title: sshd needs restarting after upgrading
On 2/16/20 7:47 PM, Gaetan Bisson via arch-dev-public wrote:
> Dear all,
>
> I'd like to post the following news item within the hour.
>
>
>
> Title: sshd needs restarting after upgrading to openssh-8.2p1
>
> Conent: After upgrading to openssh-8.2p1, the existing SSH daemon will
>
Dear all,
I'd like to post the following news item within the hour.
Title: sshd needs restarting after upgrading to openssh-8.2p1
Conent: After upgrading to openssh-8.2p1, the existing SSH daemon will
be unable to accept new connections. When upgrading remote
hosts, ple
9 matches
Mail list logo