From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH proxmox-secure-boot-support] ship apt pinning snippet
Date: Fri, 21 Jun 2024 11:22:58 +0200 [thread overview]
Message-ID: <c58bc995-6e60-418c-9439-2ce3f8565a46@proxmox.com> (raw)
In-Reply-To: <20240621070417.140682-1-f.gruenbichler@proxmox.com>
On 21/06/2024 09:04, Fabian Grünbichler wrote:
> this should ensure that a shim-signed package from a non-Proxmox repository
> cannot overtake ours, even if the version is newer. since
> proxmox-secure-boot-support is optional, this is entirely opt-in.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> not the most elegant solution, but the only one I could come up with. the next
> bookworm point release will likely ship with a shim-signed version higher than
> our current one, so we probably want to roll this out rather fast..
>
> debian/99-proxmox-secure-boot-support | 7 +++++++
> debian/proxmox-secure-boot-support.install | 1 +
> 2 files changed, 8 insertions(+)
> create mode 100644 debian/99-proxmox-secure-boot-support
> create mode 100644 debian/proxmox-secure-boot-support.install
>
>
applied, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-06-21 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 7:04 [pve-devel] " Fabian Grünbichler
2024-06-21 9:22 ` Thomas Lamprecht [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=c58bc995-6e60-418c-9439-2ce3f8565a46@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal