Add optional support for GOST 2012 DNSSEC (RFC 9558)
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
- Área
- networking, security
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
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-resolvedin an isolated network environment. - Verification that correctly signed DNS responses are accepted with
AD=1. - Verification that invalid GOST signatures are rejected with
SERVFAILandAD=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
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de systemd/systemd
-
login
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
hwdb needs-patch
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
systemd/systemd#44825 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
cryptsetup
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
documentation pid1
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Los mantenedores suelen responder en 1 día
-
needs-better-log-message network RFE 🎁
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
systemd/systemd#44563 · 4 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de systemd/systemd
Issues similares
-
polish
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
ChupathingyCE/chupathingyce#1366 ·
Los mantenedores suelen responder en 1 día
-
slice track:dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Life-Framework/Life-Framework#1831 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
-
bug intrinsic low priority wrong result
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día