Add optional support for GOST 2012 DNSSEC (RFC 9558)

Abierto
#44,415 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c

Línea de trabajo

Start by reading RFC 9558 and the issue’s description of the existing implementation and test coverage. The issue does not name systemd files or test entry points, and maintainers have not yet decided whether a libgcrypt- or OpenSSL-based approach is preferred. Done would include GOST DNSKEY, RRSIG verification, and DS digest validation with regression tests, while accepting valid signatures and rejecting invalid ones.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

resolve RFE 🎁
Component

systemd-resolved

Is your feature request related to a problem? Please describe

Hello,

We would like to propose adding support for DNSSEC algorithm 23 (GOST R 34.10-2012) and DS digest type 5 (GOST R 34.11-2012), as specified in [RFC 9558](https://www.rfc-editor.org/rfc/rfc9558.html).

RFC 9558 describes the use of Russian GOST 2012 cryptographic algorithms in DNSSEC.

We have already implemented this functionality in [NICE.OS Linux](https://niceos.ru) and successfully tested it with two cryptographic backends:

  • libgcrypt — native GOST 2012 support without additional cryptographic engines.
  • OpenSSL — working implementation that requires an additional GOST engine.

Our implementation supports GOST 2012 DNSKEY, RRSIG signature verification, and DS digest validation.

We have successfully completed:

  • RFC 9558 cryptographic test vectors.
  • Positive and negative signature verification tests.
  • Integration testing with systemd-resolved in an isolated network environment.
  • Verification that correctly signed DNS responses are accepted with AD=1.
  • Verification that invalid GOST signatures are rejected with SERVFAIL and AD=0.
  • Testing of the compiled RPM binaries.

Both implementations are functional, but we prefer libgcrypt, as it provides the required GOST algorithms natively without an additional OpenSSL GOST engine.

We would like to contribute our implementation to upstream systemd.

Before submitting a pull request, we would appreciate feedback from the maintainers on whether a libgcrypt-based implementation would be acceptable, or whether integration through OpenSSL would be preferred.

We are ready to prepare a clean upstream patch with the implementation and regression tests.

Thank you!

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

The systemd version you checked that didn't have the feature you are asking for

No response

Lenguaje dominante
C
Estrellas
17k
Forks
4.8k
Merge medio
2 d 10 h
PR fusionados (30 d)
342

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de systemd/systemd

Todos los issues de systemd/systemd

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.