2015 International Conference on ReConFigurable Computing and FPGAs (ReConFig) 2015
DOI: 10.1109/reconfig.2015.7393283
|View full text |Cite
|
Sign up to set email alerts
|

A universal hardware API for authenticated ciphers

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
17
0

Year Published

2016
2016
2018
2018

Publication Types

Select...
5
2

Relationship

1
6

Authors

Journals

citations
Cited by 9 publications
(17 citation statements)
references
References 4 publications
0
17
0
Order By: Relevance
“…Since protected AES implementations in [29,30], and all of this research, use a similar TI-protection strategy leveraging 8-bit datapaths and field inversions in Tower Fields, one can infer that this TI-protection technique is relatively efficient. In this research, we examine implementations of CAESAR Round 3 candidate authenticated ciphers which are fully (or nearly-fully) compliant with the CAESAR HW API for Authenticated Ciphers [9,10]. The version of ACORN at [19] enables a close-to-optimal protection against DPA using threshold implementations, since it uses a small datapath width (i.e., 8 bits), and has a maximum of two cascaded and gates in its nonlinear state update computation path.…”
Section: Discussionmentioning
confidence: 99%
See 2 more Smart Citations
“…Since protected AES implementations in [29,30], and all of this research, use a similar TI-protection strategy leveraging 8-bit datapaths and field inversions in Tower Fields, one can infer that this TI-protection technique is relatively efficient. In this research, we examine implementations of CAESAR Round 3 candidate authenticated ciphers which are fully (or nearly-fully) compliant with the CAESAR HW API for Authenticated Ciphers [9,10]. The version of ACORN at [19] enables a close-to-optimal protection against DPA using threshold implementations, since it uses a small datapath width (i.e., 8 bits), and has a maximum of two cascaded and gates in its nonlinear state update computation path.…”
Section: Discussionmentioning
confidence: 99%
“…The adoption by the CAESAR Committee of the CAESAR HW API for Authenticated Ciphers enables the definition of an interface which is applicable to all CAESAR-candidate authenticated ciphers, and is readily compatible with our DPA test bench and benchmarking processes. This API, available at [9,10], includes a protocol for all required authenticated cipher operations, as summarized above. The API also specifies an AXI-compatible external interface, shown in Figure 11, and further described in [41].…”
Section: Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…The paper describing the API for hardware implementations (Homsirikamol et al, 2015) also presents the performance results and API overhead for eight CAESAR candidates. This presented data will be discussed in details in the results section.…”
Section: Related Workmentioning
confidence: 99%
“…Although functional software requirements have been set for the CAESAR candidates, details of the hardware Application Programming Interface (API) have not yet been specified. However, the GMU Hardware API, which was introduced to provide a basis for benchmarking the hardware implementations of the CAESAR candidates, is considered as a standard amongst the hardware implementers of the CAE-SAR candidates (Homsirikamol et al, 2015). This API provides specifications for the interface (AEADcore) of the authenticated cipher-core as well as the communication protocol needed.…”
Section: Introductionmentioning
confidence: 99%