Hi,
On Sun, Nov 20, 2022 at 09:11:09PM +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Wed, Mar 03, 2021 at 10:52:39AM +0100, Ansgar wrote:
> > Source: grub2
> > Version: 2.04-16
> > Severity: normal
> > X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org
> >
> > grub2 currently
On Sun, 20 Nov 2022, Salvatore Bonaccorso wrote:
On Wed, Mar 03, 2021 at 10:52:39AM +0100, Ansgar wrote:
Source: grub2
Version: 2.04-16
Severity: normal
X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org
grub2 currently uses grub-efi-signed-* as source package names for the
S
Hi,
On Wed, Mar 03, 2021 at 10:52:39AM +0100, Ansgar wrote:
> Source: grub2
> Version: 2.04-16
> Severity: normal
> X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org
>
> grub2 currently uses grub-efi-signed-* as source package names for the
> Secure Boot signed packages. While
On Wed, Mar 03, 2021 at 10:52:39AM +0100, Ansgar wrote:
> I've Cc'ed debian-release@ as it is already past soft freeze, but I
> think just renaming the source packages would be unlikely to break
> anything.
>
That makes sense to me, and seems worth it to make the security team and
ftpmaster's life
Source: grub2
Version: 2.04-16
Severity: normal
X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org
grub2 currently uses grub-efi-signed-* as source package names for the
Secure Boot signed packages. While releasing the last security update
we found a small issue with these names:
5 matches
Mail list logo
