AdguardTeam / AdguardTeam/dnsproxy
Feature request: set encryption algorithm
- Vorherrschende Sprache
- Go
- Sterne
- 3.3k
- Forks
- 343
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Hi,
It would be very useful to be able to specify the encryption algorithms that dnsproxy can use. I've installed an instance on my router that doesn't benefit from AES instructions. So it would be good if I could force the instance to use only a specific version of TLS (1.3), the CHACHA20_POLY1305 algorithm to establish TLS connections and also the hash algorithm like SHA256.
Would it be possible to implement this?
Thank you for your attention and have a nice day!
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
No files, tests, or entry points are named. Start by locating dnsproxy’s existing TLS configuration and connection setup, then determine how algorithm selection is currently handled across its supported protocols. Done means a documented configuration can select TLS 1.3, CHACHA20_POLY1305, and SHA256 where supported, with coverage for the affected behavior.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- go
- Bereich
- cryptography, networking, security
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100