AdguardTeam / AdguardTeam/dnsproxy

Getting CRYPTO_ERROR (0x12a)

Abierto
#295 5 comentarios 0 reacciones 0 asignados Ver en GitHub
question
Lenguaje dominante
Go
Estrellas
3.3k
Forks
343
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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?

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

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.

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

Evaluación

Stack tecnológico
go
Área
networking, security
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.