Open korran opened 4 months ago
The hmac384 driver has two modes of operation: single-shot (via Hmac384::hmac()) and incremental (via Hmac384::init() and Hmac384Op::finalize()).
Hmac384::hmac() calls zeroize after it is done with the peripheral:
https://github.com/chipsalliance/caliptra-sw/blob/60d38f94d618f26c837e588a042b9551330bcc83/drivers/src/hmac384.rs#L244-L254
Hmac384Op::finalize() does not:
https://github.com/chipsalliance/caliptra-sw/blob/60d38f94d618f26c837e588a042b9551330bcc83/drivers/src/hmac384.rs#L521-L527
The hmac384 driver has two modes of operation: single-shot (via Hmac384::hmac()) and incremental (via Hmac384::init() and Hmac384Op::finalize()).
Hmac384::hmac() calls zeroize after it is done with the peripheral:
https://github.com/chipsalliance/caliptra-sw/blob/60d38f94d618f26c837e588a042b9551330bcc83/drivers/src/hmac384.rs#L244-L254
Hmac384Op::finalize() does not:
https://github.com/chipsalliance/caliptra-sw/blob/60d38f94d618f26c837e588a042b9551330bcc83/drivers/src/hmac384.rs#L521-L527