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]: Migrate MbedTLS and it's BaseCryptLib implementation into this repo. #47

Closed
kenlautner opened this issue Jan 13, 2024 · 4 comments · May be fixed by #58
Closed

[Feature]: Migrate MbedTLS and it's BaseCryptLib implementation into this repo. #47

kenlautner opened this issue Jan 13, 2024 · 4 comments · May be fixed by #58
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:high Significant with a critical impact

Comments

@kenlautner
Copy link
Contributor

kenlautner commented Jan 13, 2024

Feature Overview

Currently all crypto functionality in project MU is found in the CryptoPkg in MU_BASECORE and is free to reference for anyone consuming it. To reach our goal of having everyone move to our Shared Crypto binary system we're moving the functional crypto implementations into this repo where we'll build the binaries.

Solution Overview

Migrate the MbedTLS submodule and BaseCryptLib implementation of it to this repo.

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

@kenlautner kenlautner added type:feature-request A new feature proposal state:needs-triage Needs to triaged to determine next steps labels Jan 13, 2024
@github-actions github-actions bot added the urgency:medium Important with a moderate impact label Jan 13, 2024
@kenlautner kenlautner self-assigned this Jan 13, 2024
@kenlautner kenlautner added urgency:high Significant with a critical impact and removed urgency:medium Important with a moderate impact labels Jan 13, 2024
@kenlautner kenlautner linked a pull request Jan 31, 2024 that will close this issue
4 tasks
Copy link

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 Feb 27, 2024
Copy link

github-actions bot commented Mar 5, 2024

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 Mar 5, 2024
@kenlautner kenlautner reopened this Apr 18, 2024
@github-actions github-actions bot removed the state:stale Has not been updated in a long time label Apr 18, 2024
Copy link

github-actions bot commented Jun 3, 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 Jun 3, 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 Jun 11, 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:high Significant with a critical impact
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant