Skip to content

[DOC] FE rule update#574

Open
ekarabu wants to merge 3 commits into
mainfrom
user/ekarabulut/Fuse_rule_update
Open

[DOC] FE rule update#574
ekarabu wants to merge 3 commits into
mainfrom
user/ekarabulut/Fuse_rule_update

Conversation

@ekarabu

@ekarabu ekarabu commented Oct 2, 2025

Copy link
Copy Markdown
Contributor

No description provided.

mhatrevi
mhatrevi previously approved these changes Oct 2, 2025
@bluegate010

Copy link
Copy Markdown
Collaborator

Does this apply to 2.0 as well as 2.1? If so can it also update doc/caliptra_20/Caliptra.ocp?

@ekarabu

ekarabu commented Oct 3, 2025

Copy link
Copy Markdown
Contributor Author

@bluegate010 Does this apply to 2.0 as well as 2.1? If so can it also update doc/caliptra_20/Caliptra.ocp?
@ekarabu Yes, it applies to both.

@varuns-nvidia

Copy link
Copy Markdown
Contributor

@ekarabu could you describe the motivation for this change? The two input sources came from @ericeilertson

@bluegate010

Copy link
Copy Markdown
Collaborator

@ekarabu could you describe the motivation for this change? The two input sources came from @ericeilertson

I think with the current Cryptographic Mailbox interface this change is fine? The caller can invoke CM_RANDOM_STIR prior to asking the chip to generate field entropy.

@varuns-nvidia

Copy link
Copy Markdown
Contributor

@ekarabu could you describe the motivation for this change? The two input sources came from @ericeilertson

I think with the current Cryptographic Mailbox interface this change is fine? The caller can invoke CM_RANDOM_STIR prior to asking the chip to generate field entropy.

should that be made as a recommendation explicitly in this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants