Add optional support for GOST 2012 DNSSEC (RFC 9558)

Aperta
#44,415 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
C
Stelle
17k
Fork
4.8k
Merge medio
2g 10h
PR unite (30g)
342

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di systemd/systemd

Tutte le issue di systemd/systemd

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.