ungoogled-software/ungoogled-chromium

UDP socks5 , for quic support

Open

#3696 opened on Mar 14, 2026

View on GitHub
 (16 comments) (0 reactions) (0 assignees)Python (18,674 stars) (771 forks)batch import
enhancementhelp wantedneed info

Description

Description

Ceriousity

Who's implementing?

  • I'm willing to implement this feature myself

The problem

in the normal chrome , it doesnt support UDP / QUIC , but it exist,

see https://github.com/botswin/BotBrowser/blob/main/docs/guides/network/UDP_OVER_SOCKS5.md

he offers 2000$ and im indians , so ts literally about a year for me

im not a good C programmer, or a programmer at all, i have llm and basic english :3

i always wanted to compile the chromium project , so its a good insight for me :)

anyways clearly there is a patch for such thing ,,,, maybe its just a thing to use the AGENTS folder

libraries like https://github.com/enetx/surf support UDP over and tls mocking , but its not pratical , it causes issues for me when i scrape -__-

gemini says

Since you're targeting the Chromium project, a GitHub-style "Feature Request" needs to be highly technical and address the specific architectural barriers that have historically kept this out of the upstream code. Chromium uses a specialized issue tracker (monorail/Issue Tracker), but if you were to post this on a Chromium-based project’s GitHub (like Electron, Brave, or a custom automation fork), here is a professional, high-impact draft.

Subject: [Feature Request]: Support for SOCKS5 UDP ASSOCIATE (RFC 1928)
Description
Currently, Chromium's SOCKS5 implementation is limited to TCP CONNECT operations. This causes all UDP-based traffic—specifically QUIC (HTTP/3) and WebRTC (STUN/ICE)—to either bypass the proxy (leaking the user's real IP) or fail and fall back to TCP.

Adding support for the SOCKS5 UDP ASSOCIATE command would allow for true protocol-agnostic tunneling, ensuring network identity consistency and preventing IP leaks in security-sensitive automation and privacy contexts.

Technical Motivation
QUIC/HTTP3 Support: Without UDP tunneling, Chromium disables QUIC over SOCKS5. This increases latency as the browser is forced to use HTTP/2 over TCP.

WebRTC Privacy: WebRTC STUN probes often bypass SOCKS5 TCP proxies to discover the local reflexive transport address. UDP ASSOCIATE ensures these probes are routed through the proxy relay.

Consistency: Modern anti-detect and security research requirements demand that all egress traffic originates from the proxy IP.

Proposed Architectural Changes
//net/socket:

Extend SOCKS5ClientSocket to support the 0x03 (UDP ASSOCIATE) command.

Implement a SOCKS5UDPClientSocket adapter to handle the 10-byte SOCKS5 UDP encapsulation header (Reserved, Fragment, ATYP, Destination Address/Port) for every packet.

//net/quic:

Modify QuicSessionPool to recognize SOCKS5 endpoints as UDP-capable, preventing the automatic fallback to TCP-based protocols.

//third_party/webrtc:

Update rtc_base/socket_adapters.cc to include a SOCKS5 UDP variant of the AsyncProxyServerSocket.`````

Possible solutions

Alternatives

my alternative is being 10 year network seniour lol

Additional context

No response

Contributor guide

Tech stack
cpp
Domain
securityperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
C++Chromium network stackSOCKS5 RFC 1928QUIC protocol
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
The issue requests adding UDP SOCKS5 support for QUIC in ungoogled chromium. Key areas to investigate: the existing SOCKS5 TCP implementation in //net/socket, the QUIC session pool in //net/quic, and the WebRTC socket adapters in //third party/webrtc/rtc base. The author referenced a patch from botswin/BotBrowser that implements UDP over SOCKS5; reviewing that patch and evaluating its applicability to ungoogled chromium's codebase is critical. Maintainers should clarify the desired scope: whether full RFC 1928 UDP ASSOCIATE is required or a simpler approach, and whether QUIC fallback behavior should be modified. The 16 comments likely contain further discussion; they should be reviewed for technical constraints or prior attempts.