Skip to content

Conversation

@ndubchak
Copy link
Contributor

πŸ” Description

What is this PR about? feature/doc/engineering/bug?

πŸ€” Rationale

Why is this PR needed?

πŸ“ Checks

πŸ“Œ Follow-ups

TODO:

  • #0000

πŸ—’οΈ Notes

@ndubchak ndubchak force-pushed the user/ndubchak/custom-pcrlock branch 4 times, most recently from 7b2debf to dfedb0b Compare December 23, 2025 22:21
@ndubchak ndubchak force-pushed the user/ndubchak/custom-pcrlock branch from dfedb0b to 24cd0c3 Compare January 2, 2026 20:39
@ndubchak ndubchak force-pushed the user/ndubchak/custom-pcrlock branch from 7c8042d to 3361fa6 Compare January 13, 2026 17:44
@ndubchak
Copy link
Contributor Author

Closing this PR as this is no longer necessary; encryption and manual rollback flow can be enabled in the following way: #460.

Unable to solve the boot using a custom pcrlock.json, too. We might want this in the future, so summarizing the investigation below:
Custom pcrlock JSON debugging.txt

@ndubchak ndubchak closed this Jan 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants