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

CTR_DRBG is limited to AES #63

Closed
Thuffir opened this issue Feb 7, 2014 · 3 comments
Closed

CTR_DRBG is limited to AES #63

Thuffir opened this issue Feb 7, 2014 · 3 comments
Labels
component-crypto Crypto primitives and low-level interfaces enhancement historical-reviewed Reviewed & agreed to keep legacy PR/issue

Comments

@Thuffir
Copy link
Contributor

Thuffir commented Feb 7, 2014

The module CTR_DRBG could be reworked to be able to use other block cyptos than only AES (like the HASH_DRBG module). This would make the module more future proof.
@pjbakker
Copy link
Contributor

This is something we might do in the future.

@RonEld RonEld added the component-crypto Crypto primitives and low-level interfaces label Feb 17, 2019
hanno-becker pushed a commit to hanno-becker/mbedtls that referenced this issue Nov 17, 2020
Merge pull request Mbed-TLS#63 from hannestschofenig/server-only-build
e512d79 
Ensure correct server-only build
@tom-daubney-arm tom-daubney-arm added the historical-reviewing Currently reviewing (for legacy PR/issues) label Nov 25, 2022
@tom-daubney-arm
Copy link
Contributor

Since CTR_DRBG is defined by NIST then the ciphers should be NIST approved. At present the only NIST approved block cipher is AES.

@tom-daubney-arm tom-daubney-arm closed this as not planned Won't fix, can't repro, duplicate, stale Nov 30, 2022
@tom-daubney-arm tom-daubney-arm added historical-reviewed Reviewed & agreed to keep legacy PR/issue and removed historical-reviewing Currently reviewing (for legacy PR/issues) labels Nov 30, 2022
@gilles-peskine-arm
Copy link
Contributor

Actually, this is probably going to happen soon-ish, as part of the move to more PSA support.

Since CTR_DRBG is defined by NIST then the ciphers should be NIST approved

No, there's no particular reason for that. Camellia and ARIA are designed to be drop-in replacements for AES.

@ronald-cron-arm ronald-cron-arm mentioned this issue Apr 12, 2024
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component-crypto Crypto primitives and low-level interfaces enhancement historical-reviewed Reviewed & agreed to keep legacy PR/issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@mpg @pjbakker @Thuffir @RonEld @gilles-peskine-arm @tom-daubney-arm