Always gather MBEDTLS_ENTROPY_BLOCK_SIZE bytes of entropy #293
No reviewers
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto!293
Loading…
Reference in a new issue
No description provided.
Delete branch "entropy-min"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Enforce that
mbedtls_entropy_funcgathers a total ofMBEDTLS_ENTROPY_BLOCK_SIZEbytes or more from strong sources. In particular, in the default configuration, on a platform with a single entropy source,mbedtls_entropy_funcwill now grab 64 bytes from that source (due to the new lower bound ofMBEDTLS_ENTROPY_BLOCK_SIZE), whereas it formerly only grabbed 32 bytes (due to the per-source threshold).Backports: no — this is a security improvement but not a critical fix (32 bytes is enough if the entropy is of good quality) and it could be a problem on platforms where gathering more entropy would take an unacceptable amount of time.
Internal ref: IOTCRYPT-454
Is it possible to reach
ENTROPY_MAX_LOOPhere ifctx->source[i].strong == MBEDTLS_ENTROPY_SOURCE_STRONGisfalse? There's no way to increasestrong_sizein such case.Yes, but only if there is no strong source. And in this case the call to
entropy_gather_internalwould have returnedMBEDTLS_ERR_ENTROPY_NO_STRONG_SOURCE.The CI failures are not just due to unrelated problems that plagued the CI for the past few months. I'm investigating.
The CI seems to still be failing in strange ways. Are these fails related to the PR?
I think many jobs are failing on -head because it's an old branch that's broken on some boards and incompatible with the current version in mbedtls. Since -merge is passing, the CI is ok.