AdguardTeam / AdguardTeam/dnsproxy
Getting CRYPTO_ERROR (0x12a)
- 主要语言
- Go
- 星标
- 3.3k
- 派生
- 343
- PR 合并指标
- 30 天内没有已合并 PR
描述
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?
贡献指南
这个仓库没有索引到贡献指南
调研方向
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.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- go
- 领域
- networking, security
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100