Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
H
HW_CTF
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
spook
HW_CTF
Commits
50f3202c
Commit
50f3202c
authored
Apr 28, 2020
by
Momin Charles
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
add overview schematics + small fixes
parent
3be31198
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
2 additions
and
30 deletions
+2
-30
README.md
README.md
+2
-30
spook_msk/schematics/spook_HW_framework.jpg
spook_msk/schematics/spook_HW_framework.jpg
+0
-0
No files found.
README.md
View file @
50f3202c
...
...
@@ -199,7 +199,7 @@ The expected outputted commands flows for each instruction are shown in the next
<div
align=
"center"
>


</div>
...
...
@@ -220,35 +220,7 @@ It also compute the `data_validity` of each raw data command which is simply a v
It receives the digested data, encode these according to the API and outputs these.
+
**Datapath**
: This module contains all the circuitry related to the computation required to perform a call of Spook.
More particularly, it is composed by raw data holders (e.g., for the long term key), routing
logic (i.e., muxes) and the logic for the primitives Shadow and Clyde.
The protected and unprotected implementations mainly differ by the way the datapath is implemented.
We present next the architecctures tor the both flavours.
## Spook Unprotected Architecture (outdated, need to be updated with v2)
Here is described the architecture of the datapth for the unprotected Spook HW core. The latter is
optimized in order to reduce the logic cost of both Shadow and Clyde primitives while keeping
high performances.
<div
align=
"center"
>

</div>
For this purpose, the Shadow's Round A and Round B are perfomed in multiple clock cycle
by operating over 128 parts of the state. The Round A logic is re-used to compute the round function
of Clyde. In this configuration, the practical cost of Clyde boils down to the logic required to compute
the tweakey. The tag verification mechanism computes the expected tag value (as for an encryption process) and
compare its value with the tag candidate received (which is hold in a specific raw data holder).
A more detailed explanation can be found in the TOSC paper.
While the provided code implements the architecture described above, it offers the possiblity to easily modify the
serialisation level of the Shadow's Round B. This is done by modifying the generation parameter
`PDRB`
in the
[
datapath
](
/Spook_CustomApi/hdl/mode_hdl/datapath.v
)
file. More info about the
impact of this parameter can be found in the
[
primitive core
](
/Spook_CustomApi/hdl/prim_hdl/prim_core_1R_UMSK_opt_dp.v
)
file.
logic (i.e., muxes) and the logic for the primitives Shadow and Clyde.
## Spook Protected Architecture
...
...
spook_msk/schematics/spook_HW_framework.jpg
0 → 100644
View file @
50f3202c
40 KB
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment