openssl/openssl

RFC 5297: Support for AES-SIV-384 and AES-SIV-512

Open

#26,077 opened on Nov 27, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C (11,262 forks)batch import
help wantedtriaged: feature

Repository metrics

Stars
 (30,157 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

In the 2008 RFC 5297, it outlines AES-SIV-256, AES-SIV-384, and AES-SIV-512. AES-SIV-256 has already been added to OpenSSL along with smaller keys, but the increased sizes are not. Beyond this RFC, certain Wi-Fi Alliance specifications, such as EasyConnect, require AES-SIV for encryption. The lowest key length required by the specification is AES-SIV-256, with additional options including AES-SIV-384 and AES-SIV-512. Adding these ciphers would make it much simpler to implement full conformance with these specifications.

Contributor guide

Research direction
Study RFC 5297 for AES SIV 384 and AES SIV 512. Examine the existing AES SIV 256 implementation in OpenSSL to understand the structure and patterns. Add support for the new key sizes by extending the current implementation, ensuring compliance with the RFC.
Tech stack
c
Domain
security
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
CCryptographyOpenSSL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25