From mboxrd@z Thu Jan  1 00:00:00 1970
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Feedback on Core Update 157 testing
Date: Fri, 21 May 2021 18:57:27 +0200
Message-ID: <ca3c68b159ff17fb1d12439e87eda805217763c0.camel@ipfire.org>
In-Reply-To: <61B571E8-C905-48D4-9C11-A35E4391B800@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6730022035929043322=="
List-Id: <development.lists.ipfire.org>

--===============6730022035929043322==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Michael,

Am Freitag, dem 21.05.2021 um 14:08 +0100 schrieb Michael Tremer:
> Hello,
>=20
> I ran into this, too, but I didn=E2=80=99t investigate it.
>=20
> Does this only affect updates that ship a new version of OpenSSH or
> all of them?
It appears that sshd_config has been overwritten and SSH operates right
away (before a reboot) via default port 22 even 222 has been
configured. SSH have no entry in backup/includes and as far as i can
see it is also missing in the exclude file, may the configuration
directory has simply been renewed ?

>=20
> > On 21 May 2021, at 13:14, ummeegge <ummeegge(a)ipfire.org> wrote:
> >=20
> > Hi all,
> > the update went flawlessly. After the update, SSH doesn=C2=B4t respond,
> > needed to restart it via WUI to bring it back to life.
> > Has Pmacct been merged for Core 157 so far ? If yes, it does not
> > appear
> > in Pakfire.
>=20
> Pmacct has been merged and has been built:
>=20
> =C2=A0   =20
> https://nightly.ipfire.org/master/2021-05-18%2012:51:59%20+0000-d267131b/x8=
6_64/packages/pmacct-1.7.6-1.ipfire
>=20
> Can you try running =E2=80=9Cpakfire update=E2=80=9D and see if it shows up?
Thanks, this was my fault :-) .

>=20
> -Michael
>=20
> >=20
> > Some informations from here.
> >=20
> > Best,
> >=20
> > Erik
> >=20
>=20



--===============6730022035929043322==--