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

enki should skip duplicate keys when importing custom keys #2432

Open
jimmykarily opened this issue Apr 4, 2024 · 1 comment
Open

enki should skip duplicate keys when importing custom keys #2432

jimmykarily opened this issue Apr 4, 2024 · 1 comment
Labels
triage Add this label to issues that should be triaged and prioretized in the next planning call

Comments

@jimmykarily
Copy link
Contributor

In case the user imported our keys manually before exporting all of the from UEFI, or in case they forgot to skip the microsoft certs and they were already there in the custom keys, it would be good if enki checked what keys have been imported and skipped duplicates.

@jimmykarily jimmykarily added the triage Add this label to issues that should be triaged and prioretized in the next planning call label Apr 4, 2024
@ci-robbot
Copy link
Collaborator

Hello! I'm a bot, an experiment of @mudler and @jimmykarily.

To help us better understand and address your issue, please provide the following information:

  1. A clear and detailed description of the issue.
  2. The steps to reproduce the issue (if it's a bug).
  3. The versions of the relevant artifacts being used (for reference).

Please add this information to your issue, and then mention "@kairos-io-github-audit-bot" so that I can review and update the labels accordingly.

Also, the current labels on your issue are:

  • [triage]

Once you provide the necessary details, I can update the labels more accurately. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Add this label to issues that should be triaged and prioretized in the next planning call
Projects
Status: No status
Development

No branches or pull requests

2 participants