From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: sbctl: update, add kernel hook
Date: Thu, 01 Feb 2024 01:43:51 +0100 [thread overview]
Message-ID: <20240201004351.D00FE24662@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46165@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/pull/46165#issuecomment-1920261433
Comment:
> i realised the program by default writes key material to /usr/share.
> make it use /etc/secureboot instead, via a go_ldlfag
Sucks that its in `/usr/share`, but breaking already existing installs and diverting from the documentation doesn't seem right.
Upstream issue https://github.com/Foxboron/sbctl/issues/57.
next prev parent reply other threads:[~2024-02-01 0:43 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 20:39 [PR PATCH] sbctl: update to 0.11, patch, " dkwo
2023-09-20 22:27 ` Duncaen
2023-09-20 22:27 ` Duncaen
2023-09-20 22:28 ` Duncaen
2023-09-21 15:59 ` dkwo
2023-09-21 16:09 ` Duncaen
2023-09-21 18:11 ` [PR PATCH] [Updated] " dkwo
2023-09-21 18:12 ` dkwo
2023-09-21 18:16 ` Duncaen
2023-09-21 18:22 ` Duncaen
2023-09-21 18:22 ` Duncaen
2023-09-21 18:22 ` Duncaen
2023-09-21 18:23 ` Duncaen
2023-09-21 18:24 ` Duncaen
2023-09-21 20:09 ` [PR PATCH] [Updated] " dkwo
2023-09-21 20:09 ` dkwo
2023-09-23 13:06 ` [PR REVIEW] " classabbyamp
2023-09-23 14:59 ` [PR PATCH] [Updated] " dkwo
2023-09-23 15:00 ` [PR REVIEW] " dkwo
2023-09-23 20:59 ` [PR PATCH] [Updated] " dkwo
2023-09-23 21:00 ` dkwo
2023-10-11 18:48 ` dkwo
2023-10-26 22:08 ` [PR PATCH] [Updated] " dkwo
2023-10-26 22:13 ` dkwo
2023-10-27 19:50 ` [PR PATCH] [Updated] " dkwo
2023-10-27 20:22 ` dkwo
2023-10-27 20:25 ` sbctl: update to 0.12, " dkwo
2023-10-27 20:25 ` dkwo
2023-11-02 14:54 ` dkwo
2023-12-21 9:13 ` [PR PATCH] [Updated] " dkwo
2023-12-27 16:18 ` dkwo
2023-12-27 18:41 ` dkwo
2024-01-07 14:17 ` [PR PATCH] [Updated] sbctl: update, " dkwo
2024-01-16 17:03 ` dkwo
2024-01-16 22:41 ` dkwo
2024-01-16 22:42 ` [PR PATCH] [Updated] " dkwo
2024-01-25 19:38 ` dkwo
2024-01-25 19:40 ` dkwo
2024-01-25 19:42 ` [PR PATCH] [Updated] " dkwo
2024-01-25 19:46 ` dkwo
2024-01-30 22:51 ` dkwo
2024-02-01 0:42 ` Duncaen
2024-02-01 0:43 ` Duncaen
2024-02-01 0:43 ` Duncaen [this message]
2024-02-01 16:06 ` dkwo
2024-02-01 17:27 ` Duncaen
2024-02-02 22:36 ` [PR PATCH] [Updated] " dkwo
2024-02-02 22:40 ` dkwo
2024-02-02 22:40 ` dkwo
2024-04-17 19:53 ` [PR PATCH] [Updated] " dkwo
2024-04-17 19:58 ` dkwo
2024-05-11 20:18 ` [PR PATCH] [Updated] sbctl: update dkwo
2024-05-11 21:55 ` dkwo
2024-07-31 11:59 ` Calandracas606
2024-07-31 14:58 ` [PR PATCH] [Updated] " dkwo
2024-07-31 15:17 ` dkwo
2024-07-31 17:56 ` Foxboron
2024-08-01 9:32 ` [PR PATCH] [Updated] " dkwo
2024-08-01 9:35 ` dkwo
2024-08-05 8:17 ` dkwo
2024-08-07 3:49 ` classabbyamp
2024-08-07 8:59 ` [PR PATCH] [Updated] " dkwo
2024-08-07 9:08 ` dkwo
2024-08-07 10:20 ` [PR PATCH] [Merged]: " classabbyamp
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=20240201004351.D00FE24662@inbox.vuxu.org \
--to=duncaen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).