From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: updated ovpn-crl-updater script was not shipped in CU186. Needs to be added to CU187 Date: Mon, 08 Jul 2024 16:38:42 +0100 Message-ID: In-Reply-To: <63816587-29ca-419f-8cd5-91ee8e28d4a5@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3713049605064137975==" List-Id: --===============3713049605064137975== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable How many users are we talking about? I would like to close the update now anyways and release it into testing this= week. That being said, we are probably looking at a release in the last week= of July or later=E2=80=A6 We could also patch the previous update and release a new updater. Best, -Michael > On 4 Jul 2024, at 15:29, Adolf Belka wrote: >=20 > Hi Michael, >=20 > I have been asked in a private forum message (not sure why they made it pri= vate), about whether CU187 should be made an emergency update just for the ov= pn-crl-updater due to the numbers of people who might lose their OpenVPN conn= ections if the crl cannot be updated. >=20 > I pointed out that CU187 was close to being released for Testing and that c= hanging everything would probably create more issues and chaos and delay CU18= 7 which has quite a few updates related to CVE fixes. >=20 > Anyway, I thought I would forward the request to see what you think the bes= t approach would be. >=20 > Regards, > Adolf. >=20 > On 04/07/2024 15:10, Adolf Belka wrote: >> Hi Michael, >>=20 >> The ovpn-crl-updater script was updated to take account of the modified lo= cation for the ovpn.cnf file but the script was missed of the list of files t= o be shipped with CU186. >>=20 >> The file needs to be included into the CU187 list to be shipped. >>=20 >> Regards, >> Adolf. >>=20 >=20 > --=20 > Sent from my laptop >=20 --===============3713049605064137975==--