Page MenuHomeFreeBSD

Axe tmp_iv.
ClosedPublic

Authored by jhb on Jan 11 2018, 12:25 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Aug 10, 11:44 PM
Unknown Object (File)
Mon, Aug 10, 11:43 PM
Unknown Object (File)
Mon, Aug 10, 10:26 PM
Unknown Object (File)
Mon, Aug 10, 1:23 AM
Unknown Object (File)
Sun, Aug 9, 4:47 PM
Unknown Object (File)
Fri, Aug 7, 11:12 PM
Unknown Object (File)
May 18 2026, 1:30 AM
Unknown Object (File)
May 18 2026, 1:30 AM
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.