Verify ECDSA P-384 support with new test - #1
Conversation
Added a new test `TestECDSAP384Support` in `attest/ecdsa_p384_test.go` to explicitly verify and prove that ECDSA P-384 keys are supported and working correctly. This test: - Sets up a simulated TPM. - Creates an ECDSA P-384 key. - Verifies the public key curve is P-384. - Signs a digest. - Verifies the signature.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This change adds a new test file
attest/ecdsa_p384_test.gocontainingTestECDSAP384Support. This test serves as a verification that ECDSA P-384 is supported by thego-attestationlibrary. It performs a full lifecycle test: key creation, public key verification, signing, and signature verification using a simulated TPM.PR created automatically by Jules for task 535873087981312367 started by @liamjm