All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Florian Larysch <fl@n621.de>
Cc: buildroot@buildroot.org, Martin Bark <martin@barkynet.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/ca-certificates: security bump to 20260816+nmu1
Date: Thu, 22 Oct 2026 13:08:58 +0200	[thread overview]
Message-ID: <atnudFwiU5Typ174@windsurf> (raw)
In-Reply-To: <20261021223000.26513-1-fl@n621.de>

Hello Florian,

On Thu, Oct 22, 2026 at 12:29:58AM +0200, Florian Larysch wrote:
> This invalidates the compromised eMudhra intermediates by blacklisting
> the roots that signed them[1][2].
> 
> Changelog: https://salsa.debian.org/debian/ca-certificates/-/blob/5bee010adca85eb867534f6445735ad5cc0dc6f3/debian/changelog
> 
> [1] https://emudhra.we-have-a-problem.com/
> [2] https://groups.google.com/a/mozilla.org/g/dev-security-policy/c/0R3XLJL6FuE
> 
> Signed-off-by: Florian Larysch <fl@n621.de>

I ended up applying this version of the fix, even though your patch
was actually not very good, to the point where it was working at all:

- The URL in the .mk file was wrong, so downloading couldn't work
- The hash file had not been updated with the tarball change
- And there was a license file change, requiring the license file hash
  to be updated as well

I fixed all of those issues, and applied to master. Thanks!

Best regards,

Thomas Petazzoni
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-10-22 11:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21 22:29 [Buildroot] [PATCH 1/1] package/ca-certificates: security bump to 20260816+nmu1 Florian Larysch
2026-10-22 11:08 ` Thomas Petazzoni via buildroot [this message]
2026-10-22 11:18   ` Florian Larysch
2026-10-23 13:21 ` Raphaël Mélotte via buildroot

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=atnudFwiU5Typ174@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fl@n621.de \
    --cc=martin@barkynet.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.