IACR Transactions on Cryptographic Hardware and Embedded Systems 2018
DOI: 10.13154/tches.v2018.i1.18-39
|View full text |Cite
|
Sign up to set email alerts
|

FPGA-based Accelerator for Post-Quantum Signature Scheme SPHINCS-256

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
2
0

Year Published

2020
2020
2025
2025

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(2 citation statements)
references
References 1 publication
0
2
0
Order By: Relevance
“…In a large-scale deployment of our system however, frequent manual interventions are not desirable, so our goal is to pick a sufficiently large 𝑛 such that the available one-time signatures to the sensor last for the sensor's lifetime. As discussed above and taking similar schemes' evaluations into account [6], we consider a frequency of one (1) signing operation per 10 seconds for simplicity. 3 Our code is available at https://github.com/PanosChtz/Black-Box-IoT We consider sensor lifetimes between 4 months as an lower and 21 years as a upper estimate (as shown in Table 5), which imply a hash chain between 2 20 and 2 26 elements respectively.…”
Section: Evaluation Setupmentioning
confidence: 99%
See 1 more Smart Citation
“…In a large-scale deployment of our system however, frequent manual interventions are not desirable, so our goal is to pick a sufficiently large 𝑛 such that the available one-time signatures to the sensor last for the sensor's lifetime. As discussed above and taking similar schemes' evaluations into account [6], we consider a frequency of one (1) signing operation per 10 seconds for simplicity. 3 Our code is available at https://github.com/PanosChtz/Black-Box-IoT We consider sensor lifetimes between 4 months as an lower and 21 years as a upper estimate (as shown in Table 5), which imply a hash chain between 2 20 and 2 26 elements respectively.…”
Section: Evaluation Setupmentioning
confidence: 99%
“…LAdm i should run the protocol with every aggregator in the group, however we present this with one aggregator for simplicity 5. This step is typically computed by a powerful device 6. To avoid redundancy, the protocol can be improved by deterministically defining a "responsible" aggregator for each transaction as discussed previously in this section.…”
mentioning
confidence: 99%