17, 2024 6:53 PM
> *To:* Chen, Qi
> *Cc:* Khem Raj ;
> openembedded-core@lists.openembedded.org; Jose Quaresma <
> jose.quare...@foundries.io>
> *Subject:* Re: [OE-core][PATCH v5 2/3] openssh: systemd notification was
> implemented upstream
>
>
>
>
>
>
&g
n Behalf Of Jose Quaresma
Sent: Wednesday, July 17, 2024 6:53 PM
To: Chen, Qi
Cc: Khem Raj ; openembedded-core@lists.openembedded.org;
Jose Quaresma
Subject: Re: [OE-core][PATCH v5 2/3] openssh: systemd notification was
implemented upstream
ChenQi mailto:qi.c...@windriver.com>> escreveu (quart
ChenQi escreveu (quarta, 17/07/2024 à(s) 10:25):
> I think the problem might be related to the "+Type=notify-reload" change
> in sshd@.service. It's in inetd mode so the upstream change about
> SYSTEMD_NOTIFY should have nothing to do with it.
> I also doubt if the following line should be remove
I think the problem might be related to the "+Type=notify-reload" change
in sshd@.service. It's in inetd mode so the upstream change about
SYSTEMD_NOTIFY should have nothing to do with it.
I also doubt if the following line should be removed from sshd.service.
-ExecReload=@BASE_BINDIR@/kill -HU
Khem Raj escreveu (quarta, 17/07/2024 à(s) 07:38):
> actually I narrowed down my problem of disconnection to this patch in
> the series. Earlier I thought it might be related to the openssh
> upgrade patch
> but reverting that still causes the problem but this patch when
> reverted, the problem i
actually I narrowed down my problem of disconnection to this patch in
the series. Earlier I thought it might be related to the openssh
upgrade patch
but reverting that still causes the problem but this patch when
reverted, the problem is gone.
On Tue, Jul 16, 2024 at 7:17 AM Jose Quaresma via
list
Still side effects of the XZ backdoor. The systemd sd-notify patch
was rejected [1] upstream and was chosen a standalone implementation
that does not depend on libsystemd [2].
Racional [1]:
License incompatibility and library bloatedness were the reasons.
Given recent events we're never going to
