Skip to content

Conversation

@siemen11
Copy link
Contributor

Use the crypto target as a dependency for the pentest framework instead of the separate targets.

@siemen11 siemen11 requested a review from cfrantz as a code owner November 25, 2025 16:51
@siemen11 siemen11 requested review from nasahlpa and removed request for cfrantz November 25, 2025 16:51
@siemen11 siemen11 added the CherryPick:earlgrey_1.0.0 This PR should be cherry-picked to earlgrey_1.0.0 label Nov 25, 2025
@siemen11 siemen11 added the CI:Rerun Rerun failed CI jobs label Nov 25, 2025
@github-actions github-actions bot removed the CI:Rerun Rerun failed CI jobs label Nov 25, 2025
@siemen11 siemen11 added the CI:Rerun Rerun failed CI jobs label Nov 25, 2025
@github-actions github-actions bot removed the CI:Rerun Rerun failed CI jobs label Nov 25, 2025
@siemen11 siemen11 requested a review from a team as a code owner November 26, 2025 10:39
@siemen11 siemen11 requested review from moidx and removed request for a team November 26, 2025 10:39
Move the header files from keyblob and integrity to include.
These functions and constants are needed for the use of the crypto
library.

Signed-off-by: Siemen Dhooghe <[email protected]>
@siemen11 siemen11 force-pushed the pentest_deps branch 3 times, most recently from 4d0e1dd to d98cbff Compare November 26, 2025 12:34
Use the crypto target as a dependency for the pentest framework instead
of the separate targets.

Signed-off-by: Siemen Dhooghe <[email protected]>
@siemen11 siemen11 force-pushed the pentest_deps branch 2 times, most recently from 8ba2f7e to 4280da6 Compare November 26, 2025 14:17

#ifndef OPENTITAN_SW_DEVICE_LIB_CRYPTO_IMPL_ECC_P384_H_
#define OPENTITAN_SW_DEVICE_LIB_CRYPTO_IMPL_ECC_P384_H_
#ifndef OPENTITAN_SW_DEVICE_LIB_CRYPTO_INCLUDE_P384_H_
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Siemen

I don't think that we simply should move the header files from the internal impl folder to the public API include folder. The reason is that we would now expose internal functions (such as p384_ecdsa_sign_start) which the user should not use by themselves.

I believe a better option would be to move functions that the user needs to use to the include folder and keep the ones the user should not use in the impl folder.

@siemen11 siemen11 marked this pull request as draft November 26, 2025 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CherryPick:earlgrey_1.0.0 This PR should be cherry-picked to earlgrey_1.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants