AdguardTeam / AdguardTeam/dnsproxy
Getting CRYPTO_ERROR (0x12a)
- Vorherrschende Sprache
- Go
- Sterne
- 3.3k
- Forks
- 343
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Hello, I'm trying to establish DNS over quic.
On my server I'm running Bind, and using bind as an upstream to the DNS proxy.
`./dnsproxy --quic-port=853 --tls-crt=myserver.crt --tls-key=myserver.key -u 127.0.0.1:53 -p 0 `
I'm running the following on my client machine to talk to dnsproxy on my server using dns over quic.
`./dnsproxy -u quic://server_ip:853 -p 53`
When I tried retrieving the record from server in my client, getting the following error at my server side proxy
`got error when accepting a new QUIC stream: CRYPTO_ERROR (0x12a): tls: bad certificate`
I have used self generated certificate. How do I solve this error?
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Rechercherichtung
Start by reproducing the server and client commands shown in the issue, using the self-generated certificate and the reported DNS-over-QUIC connection. Read the QUIC/TLS certificate-handling entry points involved in accepting a new stream; done means the client can retrieve a DNS record without the CRYPTO_ERROR, with the required certificate behavior documented or corrected.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- go
- Bereich
- networking, security
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100