public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Review of package updates from Adolf for any with CVE's
Date: Tue, 02 Jul 2024 10:00:08 +0100	[thread overview]
Message-ID: <E1FACE81-9E0A-40D5-9834-0C8946C328F8@ipfire.org> (raw)
In-Reply-To: <32e5aa16-80f1-42ef-94aa-fc04adedf80f@ipfire.org>

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

Hello,

I will merge this together now…

-Michael

> On 2 Jul 2024, at 09:57, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> I went through the list of package updates that I have provided that are not yet merged.
> 
> There are two that have CVE's.
> 
> openssh, which we know from yesterday and tshark.
> 
> Current version of tshark is 4.0.8 and there are 13 updates between that version and the update of 4.2.5.
> 
> In 7 of those 13 updates there are a total of 21 CVE's, so I think tshark definitely needs to go into CU187.
> 
> Regards,
> 
> Adolf.
> 
> -- 
> Sent from my laptop
> 


      reply	other threads:[~2024-07-02  9:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-02  8:57 Adolf Belka
2024-07-02  9:00 ` Michael Tremer [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=E1FACE81-9E0A-40D5-9834-0C8946C328F8@ipfire.org \
    --to=michael.tremer@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