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: apr is in need of an update
Date: Thu, 12 Sep 2024 14:46:06 +0200	[thread overview]
Message-ID: <266718ba-c641-4851-92eb-9f04afa322ae@ipfire.org> (raw)
In-Reply-To: <5d1598c6-d2c7-4630-b7db-2d7ae80859cb@ipfire.org>

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

Hi Peter,

On 12/09/2024 11:09, Peter Müller wrote:
> Hello development folks,
>
> as I am currently struggling to get my local build environment in a functional state again,
> I'd like to flag it here that the Apache Portable Runtime (apr) is in need of an update.
>
> Version 1.7.5 fixes CVE-2023-49582, a flaw potentially allowing local users to read named
> shared memory segments. While this doesn't sound overly alarming, my understanding is that
> since APR is relatively close to the untrusted outside, it might beneficial to update it
> sooner rather than later (and I don't exactly know when the merge window for C189 closes).
>
> If somebody is already working on this, please excuse the noise. If not, I can take care of
> it, provided that I am able to build again on my local machine before departing to London. :-)

I am not working on it and if you want to use it to get your build system working then feel free to do so. I am willing to build it if you have a problem getting your system to work, just let me know, but I will only be able to do that up to Sunday 15th September as after that I will be travelling.

Regards,

Adolf.

> Thanks, and best regards,
> Peter Müller

      reply	other threads:[~2024-09-12 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12  9:09 Peter Müller
2024-09-12 12:46 ` Adolf Belka [this message]

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=266718ba-c641-4851-92eb-9f04afa322ae@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