|author||Konrad Rzeszutek Wilk <email@example.com>||Fri Jun 11 20:24:00 2021 -0400|
|committer||Konrad Rzeszutek Wilk <firstname.lastname@example.org>||Sat Jun 12 09:04:32 2021 -0400|
GDS/LEF/GL: Import from 36322d4 GL: Copy the file without the modifications 75c1e4caaf3fbf2ef94a6b7945596393ad0fda7c gds/wrapper_sha1.gds 3f331b153e415399fa097c676bf0ecd7f91ad391 gds/wrapper_sha1.gds.png 57e7786cfedf17804e6f60b410faba09cf4c845e gds/wrapper_sha1.lef 1b771b1795e3a9ae7330223f9a2cd279a2499a14 gds/wrapper_sha1.lvs.powered.v 7e3a53e6e81c2a6668888e398444a4b7d4656b29 gds/wrapper_sha1.lvs.v Signed-off-by: Konrad Rzeszutek Wilk <email@example.com>
See a https://github.com/konradwilk/sha1 for the full git history of this code. Branch name is submission-mpw-two-c.
This is an implementation of [https://www.rfc-editor.org/rfc/inline-errata/rfc3174.html](RFC 3174) of SHA-1 engine.
It is not the most secure one nowadays (it is still used for git commit ids and TPM PCR values), but it looked like the easiest of the SHA engines to implement. The communication channel is via WishBone commands to provide sixteen words after which the engine starts and computes the digest in about 160 cycles. Then digest can be retrieved via the wishbone. There is a IRQ line so when it has completed it will bring it high if that is enabled.
If you want to see this more interactively, I would recommend you clone https://github.com/konradwilk/sha1 and run
which will use the various WishBone commands to program it.