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.

Sign up for GitHub

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

Jump to bottom

Allow taking advantage of HW-based AES block cipher #3285

Closed
zephyrbot opened this issue Mar 3, 2017 · 1 comment
Closed

Allow taking advantage of HW-based AES block cipher #3285

zephyrbot opened this issue Mar 3, 2017 · 1 comment
Labels
area: Security Security Enhancement Changes/Updates/Additions to existing features

Comments

@zephyrbot
Copy link
Collaborator

zephyrbot commented Mar 3, 2017 •
edited
Loading

Reported by Johan Hedberg:

Several platforms provide the AES-128 block cipher as a HW feature, but the modes of operation need to be implemented in software. Current TinyCrypt and the newly introduced crypto API do not cover such a use case. It should be possible to utilize a HW-based block cipher without having to write the mode of operation implementation manually every time it's needed. For the Bluetooth use cases the most important modes are CMAC and CCM.

(Imported from Jira ZEP-1837)
@zephyrbot zephyrbot added area: Security Security Enhancement Changes/Updates/Additions to existing features labels Sep 23, 2017
This was referenced Sep 23, 2017
Closed
Closed
@nashif
Copy link
Member

nashif commented Mar 18, 2020

duplicate of #2837

@nashif nashif closed this as completed Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: Security Security Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nashif @zephyrbot