All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: How to boot Windows when Bitlocker enabled with key sealed in TPM
Date: Fri, 25 Mar 2022 21:31:43 +0100	[thread overview]
Message-ID: <CAEaD8JPum1h2bFVZrVrRykUetCAtc9bLW3N9m1Q2Q_G_0kt8oQ@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtTRRxu+WWv_6KXXDhO-tzW27Tc+09fi0ocPEaG-wRd+wg@mail.gmail.com>

On Fri, Mar 25, 2022 at 9:14 PM Chris Murphy <lists@colorremedies.com> wrote:
>
> For all practical purposes, this is functionally the end to dual boot
> in GRUB, if there is no work around, e.g. bootnext. Is that the
> direction GRUB maintainers want to go in?
Why don't you just update TPM with new values? Then it will get
unsealed when booted through GRUB
>
> --
> Chris Murphy
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel



-- 
Regards
Vladimir 'phcoder' Serbinenko


  reply	other threads:[~2022-03-25 20:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 23:48 How to boot Windows when Bitlocker enabled with key sealed in TPM Chris Murphy
2022-02-09 22:08 ` Chris Murphy
2022-02-10 14:48 ` Lennart Sorensen
2022-02-10 18:46   ` Chris Murphy
2022-02-10 19:28     ` Lennart Sorensen
2022-02-10 21:13       ` Chris Murphy
2022-02-12 23:32         ` Lennart Sorensen
2022-03-25 20:13 ` Chris Murphy
2022-03-25 20:31   ` Vladimir 'phcoder' Serbinenko [this message]
2022-03-25 23:00     ` Chris Murphy
2022-03-25 23:08       ` Chris Murphy

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=CAEaD8JPum1h2bFVZrVrRykUetCAtc9bLW3N9m1Q2Q_G_0kt8oQ@mail.gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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 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.