AdguardTeam / AdguardTeam/dnsproxy

Bug Report: upstream doh queries use random tls v1.2 or v1.3 for different servers

未关闭
#509 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Go
星标
3.3k
派生
343
PR 合并指标
30 天内没有已合并 PR

描述

dnsproxy v0.82.0, Windows 11
Upstreams: IP-based DoH (no SNI), e.g. https://149.112.112.9/dns-query

Problem:
After observing random fails on accessing DoH servers, I have found out
dnsproxy negotiates TLS 1.2 with certain DoH upstreams despite those servers supporting TLS 1.3.
Setting tls-min-version: 1.3 in config has no effect on outgoing upstream connections.

Key finding:
Using a 3rd party tool, querying the exact same server, negotiates TLS 1.3 successfully. Confirmed via Wireshark on both sides. This rules out the server and points to a difference in how dnsproxy initializes its upstream HTTP client.
Expected behavior
dnsproxy should negotiate TLS 1.3 with upstreams that support it, consistent with dnslookup behavior.

Request:
Please add the ability to determine upstream tls version

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。