public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: updated ovpn-crl-updater script was not shipped in CU186. Needs to be added to CU187
Date: Thu, 04 Jul 2024 16:29:05 +0200	[thread overview]
Message-ID: <63816587-29ca-419f-8cd5-91ee8e28d4a5@ipfire.org> (raw)
In-Reply-To: <830e882a-3fe7-4f06-9ff4-eb084996cc18@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 967 bytes --]

Hi Michael,

I have been asked in a private forum message (not sure why they made it 
private), about whether CU187 should be made an emergency update just 
for the ovpn-crl-updater due to the numbers of people who might lose 
their OpenVPN connections if the crl cannot be updated.

I pointed out that CU187 was close to being released for Testing and 
that changing everything would probably create more issues and chaos and 
delay CU187 which has quite a few updates related to CVE fixes.

Anyway, I thought I would forward the request to see what you think the 
best approach would be.

Regards,
Adolf.

On 04/07/2024 15:10, Adolf Belka wrote:
> Hi Michael,
>
> The ovpn-crl-updater script was updated to take account of the 
> modified location for the ovpn.cnf file but the script was missed of 
> the list of files to be shipped with CU186.
>
> The file needs to be included into the CU187 list to be shipped.
>
> Regards,
> Adolf.
>

-- 
Sent from my laptop


  reply	other threads:[~2024-07-04 14:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 13:10 Adolf Belka
2024-07-04 14:29 ` Adolf Belka [this message]
2024-07-08 15:38   ` Michael Tremer
2024-07-08 15:53     ` Adolf Belka
2024-07-09 21:32       ` Michael Tremer
2024-07-10  7:53         ` Adolf Belka

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=63816587-29ca-419f-8cd5-91ee8e28d4a5@ipfire.org \
    --to=adolf.belka@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