From: adrian15sgd <adrian15sgd@gmail.com>
To: Askar Safin <safinaskar@zohomail.com>,
The development of GNU GRUB <grub-devel@gnu.org>
Cc: pete <pete@akeo.ie>, scdbackup <scdbackup@gmx.net>
Subject: Re: [PATCH] Change "efi" to "EFI" in grub-mkrescue for secure boot
Date: Sat, 14 Sep 2024 15:49:54 +0200 [thread overview]
Message-ID: <123d4720-7823-0e6a-e861-41e415cd73bb@gmail.com> (raw)
In-Reply-To: <191f025803e.df02b1c283554.3953018943339711108@zohomail.com>
El 14/9/24 a las 12:47, Askar Safin escribió:
> ---- On Wed, 11 Sep 2024 14:23:05 +0400 adrian15sgd wrote ---
> > No, I did not disable the SecureBoot support in Super Grub2 Disk because
> > of this "efi" to "EFI" supposed problem that you describe.
>
> I'm not talking about secure boot support in super grub disk. I'm talking about secure boot support on CD (as opposed to USB stick) in super grub disk.
>
> Currently it seems from release page ( https://www.supergrubdisk.org/2024/07/30/super-grub2-disk-2-06s4-released/ ), that secure boot downloads come as USB stick images only, not as CD. Note: I don't ASK for adding support for CDs, I'm not super grub disk user, i. e. this is not feature request. I'm just pointing that CDs are not supported, and I still suspect that that "EFI vs efi" problem is the reason.
>
> Anyway, I know how to create bootable GRUB CDs with secure boot support, so ask me if you have any questions.
>
> You can use script in my first letter ( https://lore.kernel.org/grub-devel/20240906132914.27842-1-safinaskar@zohomail.com/ ) as starting point.
>
> --
> Askar Safin
> https://types.pl/@safinaskar
Well, it seems I overlooked the 'cd' part. I thought that the commit was
only about SecureBoot and that's it.
I actually don't remember what problems I had trying to make a Super
Grub2 Disk SecureBoot CD.
I guess that I actually decided not to build a SG2D SecureBoot CD after all.
I was surprised myself a few moments early not finding one specific
download for that.
Not sure if it would be worth to create an SG2D SecureBoot CD but now I
know that it's not there. So thank you!
adrian15
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
prev parent reply other threads:[~2024-09-14 13:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 13:15 [PATCH] Change "efi" to "EFI" in grub-mkrescue for secure boot Askar Safin via Grub-devel
2024-09-06 18:09 ` Thomas Schmitt via Grub-devel
2024-09-06 21:50 ` Pascal Hambourg
2024-09-07 7:51 ` Vladimir 'phcoder' Serbinenko
2024-09-07 8:30 ` Thomas Schmitt via Grub-devel
2024-09-08 16:12 ` Pascal Hambourg
2024-09-07 7:53 ` Vladimir 'phcoder' Serbinenko
2024-09-07 10:35 ` Askar Safin via Grub-devel
2024-09-27 16:10 ` Askar Safin via Grub-devel
2024-09-27 17:42 ` Askar Safin via Grub-devel
2024-09-11 10:09 ` adrian15sgd
2024-09-11 10:23 ` adrian15sgd
2024-09-11 10:38 ` Tobias Powalowski via Grub-devel
2024-09-11 15:13 ` adrian15sgd
2024-09-11 15:46 ` Tobias Powalowski via Grub-devel
2024-09-14 11:04 ` Askar Safin via Grub-devel
2024-09-14 13:56 ` adrian15sgd
2024-09-26 20:46 ` Askar Safin via Grub-devel
2024-09-14 10:47 ` Askar Safin via Grub-devel
2024-09-14 13:49 ` adrian15sgd [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=123d4720-7823-0e6a-e861-41e415cd73bb@gmail.com \
--to=adrian15sgd@gmail.com \
--cc=grub-devel@gnu.org \
--cc=pete@akeo.ie \
--cc=safinaskar@zohomail.com \
--cc=scdbackup@gmx.net \
/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.