Re: Open security issues affecting trixie which are not RC (2025-04-29)

To: noloader@gmail.com
Cc: debian-security@lists.debian.org, debian-release@lists.debian.org
Subject: Re: Open security issues affecting trixie which are not RC (2025-04-29)
From: NoisyCoil <noisycoil@disroot.org>
Date: Tue, 29 Apr 2025 23:22:31 +0200
Message-id: <[🔎] e9accac6-6aa0-454e-968a-857319c14830@disroot.org>
In-reply-to: <[🔎] CAH8yC8mrWaxtA0kYhc+_cd4C7fdAB4DAJ0F+pS7hTEF8Wd-FGg@mail.gmail.com>
References: <[🔎] aBEWlA8xtun36tvZ@pisco.westfalen.local> <[🔎] CAH8yC8mrWaxtA0kYhc+_cd4C7fdAB4DAJ0F+pS7hTEF8Wd-FGg@mail.gmail.com>

Hi Jeff,

On 29/04/25 22:12, Jeffrey Walton wrote:

For Crpyto++, Debian should grab
<https://github.com/weidai11/cryptopp/commit/641ae35258de3977>.


Should the preceding and following commit also be picked?

Cheers!

Reply to:

References:
- Open security issues affecting trixie which are not RC (2025-04-29)
  - From: Moritz Mühlenhoff <jmm@inutil.org>
- Re: Open security issues affecting trixie which are not RC (2025-04-29)
  - From: Jeffrey Walton <noloader@gmail.com>

Prev by Date: Re: Open security issues affecting trixie which are not RC (2025-04-29)
Previous by thread: Re: Open security issues affecting trixie which are not RC (2025-04-29)
Index(es):
- Date
- Thread