Generic cipher max key length #226

Open
opened 2019-08-18 10:55:00 -05:00 by nanokatze · 2 comments
nanokatze commented 2019-08-18 10:55:00 -05:00 (Migrated from github.com)

Description

Given the existence of MBEDTLS_MAX_IV_LENGTH and MBEDTLS_MAX_BLOCK_LENGTH constants, which give upper bounds on ciphers' IV and block lengths respectively, would it be possible to add such a constant for ciphers' key lengths? A possible use case: github.com/ARMmbed/mbedtls@535ee4a35b/library/ssl_ticket.c (L55).

In the current default set of ciphers, AES 256 XTS https://github.com/ARMmbed/mbed-crypto/blob/development/library/cipher_wrap.c#L510 has the largest key of 512 bits (64 octets).

Issue request type

[ ] Question
[x] Enhancement
[ ] Bug
<!-- ************************************** WARNING ************************************** The ciarcom bot parses this header automatically. Any deviation from the template may cause the bot to automatically correct this header or may result in a warning message, requesting updates. Please ensure that nothing follows the Issue request type section, all issue details are within the Description section and no changes are made to the template format (as detailed below). ************************************************************************************* --> ### Description Given the existence of MBEDTLS_MAX_IV_LENGTH and MBEDTLS_MAX_BLOCK_LENGTH constants, which give upper bounds on ciphers' IV and block lengths respectively, would it be possible to add such a constant for ciphers' key lengths? A possible use case: https://github.com/ARMmbed/mbedtls/blob/535ee4a35b9c4ddd059451b8fa5b201bfc89fbcf/library/ssl_ticket.c#L55. In the current default set of ciphers, AES 256 XTS https://github.com/ARMmbed/mbed-crypto/blob/development/library/cipher_wrap.c#L510 has the largest key of 512 bits (64 octets). <!-- Required Add detailed description of what you are reporting. Good example: https://os.mbed.com/docs/latest/reference/workflow.html Things to consider sharing: - What target does this relate to? - What toolchain (name + version) are you using? - What tools (name + version - is it mbed-cli, online compiler or IDE) are you using? - What is the SHA of Mbed OS (git log -n1 --oneline)? - Steps to reproduce. (Did you publish code or a test case that exhibits the problem?) --> ### Issue request type <!-- Required Please add only one X to one of the following types. Do not fill multiple types (split the issue otherwise.) Please note this is not a GitHub task list, indenting the boxes or changing the format to add a '.' or '*' in front of them would change the meaning incorrectly. The only changes to be made are to add a description text under the description heading and to add a 'x' to the correct box. --> [ ] Question [x] Enhancement [ ] Bug
ciarmcom commented 2019-08-18 16:19:47 -05:00 (Migrated from github.com)

Internal Jira reference: https://jira.arm.com/browse/IOTCRYPT-873

*Internal Jira reference: https://jira.arm.com/browse/IOTCRYPT-873*
adbridge commented 2019-11-04 06:41:50 -06:00 (Migrated from github.com)

Apologies, this was closed in error by the automated bot - re-opening.

Apologies, this was closed in error by the automated bot - re-opening.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-ARMmbed/mbed-crypto#226
No description provided.