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]: Crypto On Protocol Support #871

Open
apop5 opened this issue May 24, 2024 · 1 comment · Fixed by #951
Open

[Feature]: Crypto On Protocol Support #871

apop5 opened this issue May 24, 2024 · 1 comment · Fixed by #951
Assignees
Labels
type:feature-request A new feature proposal urgency:low Little to no impact

Comments

@apop5
Copy link
Contributor

apop5 commented May 24, 2024

Feature Overview

Crypto On Protocol Support

Solution Overview

Crypto On Protocol Support

Alternatives Considered

No response

Urgency

Low

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

@apop5 apop5 added state:needs-triage Needs to triaged to determine next steps type:feature-request A new feature proposal labels May 24, 2024
@github-actions github-actions bot added the urgency:low Little to no impact label May 24, 2024
@makubacki makubacki self-assigned this Jun 3, 2024
@makubacki makubacki removed the state:needs-triage Needs to triaged to determine next steps label Jun 3, 2024
@makubacki
Copy link
Member

If I understand correctly, this is referencing BaseCryptLibOnProtocolPpi which is already in edk2.

I would like to track some recent changes I made for Standalone MM and Runtime DXE, so I'll reuse this feature unless there was something else to it.

@makubacki makubacki linked a pull request Jun 26, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature-request A new feature proposal urgency:low Little to no impact
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants