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

[Feature]: Check the DB for the existence of the new certificate before appending #368

Closed
Flickdm opened this issue Nov 21, 2023 · 2 comments
Assignees
Labels
state:needs-triage Needs to triaged to determine next steps state:stale Has not been updated in a long time type:feature-request A new feature proposal urgency:medium Important with a moderate impact

Comments

@Flickdm
Copy link
Member

Flickdm commented Nov 21, 2023

Feature Overview

Secure Boot Recovery Application should check for the existence of the 2023 Production CA and if it's found respect the existing boot order.

This would prevent scenarios where the application appended correctly yet for some reason the device is continuing to loop.

Solution Overview

  1. Loop over each certificate found in the DB
  2. for each certificate, determine if it has enough length to compare against a #define thumbprint and subject name
  3. compare against the #define thumbprint and subject name
  4. if so return EFI_UNSUPPORTED

Alternatives Considered

No response

Urgency

Medium

Are you going to implement the feature request?

I will implement the feature

Do you need maintainer feedback?

No maintainer feedback needed

Anything else?

No response

@Flickdm Flickdm added state:needs-triage Needs to triaged to determine next steps type:feature-request A new feature proposal labels Nov 21, 2023
@Flickdm Flickdm self-assigned this Nov 21, 2023
@github-actions github-actions bot added the urgency:medium Important with a moderate impact label Nov 21, 2023
Copy link

github-actions bot commented Jan 5, 2024

This issue has been automatically marked as stale because it has not had activity in 45 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.

@github-actions github-actions bot added the state:stale Has not been updated in a long time label Jan 5, 2024
Copy link

This issue has been automatically been closed because it did not have any activity in 45 days and no follow up within 7 days after being marked stale. Thank you for your contributions.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:needs-triage Needs to triaged to determine next steps state:stale Has not been updated in a long time type:feature-request A new feature proposal urgency:medium Important with a moderate impact
Projects
None yet
Development

No branches or pull requests

1 participant