Skip to main navigation Skip to search Skip to main content

Towards Finding Best Linear Codes for Side-Channel Protections

  • Institut Polytechnique de Paris
  • Secure-IC SAS

Research output: Contribution to journalConference articlepeer-review

1 Citation (Scopus)

Abstract

Side-channel attacks aim at extracting secret keys from cryptographic devices. Randomly masking the implementation is a provable way to protect the secrets against this threat. Recently, various masking schemes have converged to the “code-based masking” philosophy. In code-based masking, different codes allow for different levels of side-channel security. In practice, for a given leakage function, it is important to select the code which enables the best resistance, i.e., which forces the attacker to capture and analyze the largest number of side-channel traces. This paper is a first attempt to address the constructive selection of the optimal codes in the context of side-channel countermeasures, in particular for code-based masking when the device leaks information in the Hamming weight leakage model. We show that the problem is related to the weight enumeration of the extended dual of the masking code. We first present mathematical tools to study those weight enumeration polynomials, and then provide an efficient method to search for good codes, based on a lexicographic sorting of the weight enumeration polynomial from lowest to highest degrees.

Original languageEnglish
Pages (from-to)83-99
Number of pages17
JournalEPiC Series in Computing
Volume87
DOIs
Publication statusPublished - 1 Jan 2022
Event10th International Workshop on Security Proofs for Embedded Systems, PROOFS 2021 - Beijing, China
Duration: 17 Sept 202117 Sept 2021

Keywords

  • Information-Theoretic Metric
  • Linear Code
  • Masking Scheme
  • Security Formalization
  • Side-Channel Analysis
  • Weight Distribution

Fingerprint

Dive into the research topics of 'Towards Finding Best Linear Codes for Side-Channel Protections'. Together they form a unique fingerprint.

Cite this