Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retest the solution on Intel hardware with TPM 1.2 and TPM 2.0 using legacy boot mode #18

Closed
BeataZdunczyk opened this issue Apr 3, 2023 · 3 comments
Assignees
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: feature request Type: feature reguest. A new feature for the project. W: done Workflow: done. This issue is done/close.

Comments

@BeataZdunczyk
Copy link
Member

Is your feature request related to a problem? Please describe.

It is necessary to retest the solution on Intel hardware with TPM 1.2 and TPM 2.0 using legacy boot mode to ensure proper functionality after updating the TrenchBoot support in Qubes OS AEM.

Is your feature request related to a new idea or technology that
would benefit the project? Please describe.

This issue is required to ensure that the TrenchBoot support continues to work properly on Intel hardware with TPM 1.2 and TPM 2.0 using legacy boot mode after the code rebase onto the most recent work implementing Secure Launch protocol being upstreamed to Linux and GRUB implementation (#17).

Describe the solution you'd like

Retest the TrenchBoot support on Intel hardware with TPM 1.2 and TPM 2.0 using legacy boot mode after the code rebase onto the most recent work implementing Secure Launch protocol being upstreamed to Linux and GRUB to ensure proper functionality.

Describe alternatives you've considered

N/A

Additional context

This feature request is part of Phase 3 in TrenchBoot as Anti Evil Maid project, as outlined in the documentation: https://docs.dasharo.com/projects/trenchboot-aem-v2/.

Relevant documentation you've consulted

N/A

@BeataZdunczyk BeataZdunczyk added T: feature request Type: feature reguest. A new feature for the project. P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. W: todo Workflow: todo. The issue is in the initial to do state. labels Apr 3, 2023
@krystian-hebel
Copy link

There is an issue with installation in legacy mode for R4.2.0, but rc3 still works.

Tests on HP Elitedesk 800 G2 with TPM 2.0 were successful:
image-20240108-153132
image-20240108-153140
image-20240108-153147
image-20240108-153156
image-20240108-153205

There are only two small issues, I'll describe them in the blog post, but I don't think they are blocking this release:

@BeataZdunczyk BeataZdunczyk added W: in progress Workflow: in progress. The issue is actively being worked on. and removed W: todo Workflow: todo. The issue is in the initial to do state. labels Jan 10, 2024
@krystian-hebel
Copy link

Tests on Optiplex with TPM 1.2 were also successful:
image
image
image

Issue with SLAUNCH_START/_END not being used is still present, but we bumped qubes-antievilmaid version so it should be safe against the updates for now. This was retested on HP with no visible difference. Both TPM 1.2 and TPM 2.0 platforms work as expected on release binaries:

@BeataZdunczyk
Copy link
Member Author

Closing this issue as both platforms have been successfully tested. An in-depth summary of the work conducted in milestone Phase 3: Update to the newest TrenchBoot boot protocol is available here: https://blog.3mdeb.com/2024/2024-01-12-aem_phase3/.

@BeataZdunczyk BeataZdunczyk added W: done Workflow: done. This issue is done/close. and removed W: in progress Workflow: in progress. The issue is actively being worked on. labels Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. T: feature request Type: feature reguest. A new feature for the project. W: done Workflow: done. This issue is done/close.
Projects
None yet
Development

No branches or pull requests

2 participants