Page MenuHomeFreeBSD

Axe tmp_iv.
ClosedPublic

Authored by jhb on Jan 11 2018, 12:25 AM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 4 2024, 9:20 PM
Unknown Object (File)
Nov 26 2024, 1:41 AM
Unknown Object (File)
Oct 3 2024, 6:29 PM
Unknown Object (File)
Oct 3 2024, 7:25 AM
Unknown Object (File)
Sep 27 2024, 8:19 PM
Unknown Object (File)
Sep 19 2024, 7:44 AM
Unknown Object (File)
Sep 8 2024, 4:17 AM
Unknown Object (File)
Sep 5 2024, 11:52 PM
Subscribers

Details

Summary

Just copyin the IV into the crypto descriptor directly.

This avoids copying the IV twice for each operation.

Test Plan
  • have run my cryptocheck tool against this numerous times, but also requests from OpenSSL's engine

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Does this mean that crd_iv potentially contains unknown data ? E.g. after the partial copy + fault.

Perhaps it is fine because the content of crd_iv is user-controlled anyway.

This revision is now accepted and ready to land.Jan 11 2018, 11:13 AM

crd_iv is only used after the copyin() if it succeeds. It shouldn't have any different data as a result of this change once a request is submitted to the driver.

This revision was automatically updated to reflect the committed changes.