Proxies will die in 2023?

[Bers666]

Hi, there is a concern about raising usage of QUIC protocol (HTTP 3.0) with combination of using a proxy in browser. QUIC is UDP. All modern browsers do support QUIC. Yet none of them support sending QUIC via a proxy. Even if the proxy itself can send UDP (most Socks5 proxies can't but some can!).

And when a website finds out you have a modern browser and can't send QUIC, it's a big red flag to consider you are a bot!

3rd party solutions like Proxifier don't support sending QUIC either.

Possible solutions:

- wait till browsers can send QUIC via a proxy + proxy providers start adding UDP to their proxies
- wait till tools like Proxifier can forward browser's UDP traffic via SOCKS5
- switch to 4G\5G VPN which are way more expensive.

 

[OccultKingdoms]

I'm yet waiting for that IPv6 implementation.

Possible solutions:

Let proxy providers do their job and adapt to the market. If they don't evolve, they will just die. And I wouldn't believe they won't figure this out.

 

[Bers666]

Let proxy providers do their job and adapt to the market.

what do you mean? Imagine most of them support Socks5/UDP now. But browser's can't send HTTP3 via any proxy now. So eventhough proxy providers adapted, it is useless.

 

[protonch]

He has a solution too

Changelog:
1. New Edge 107/108 Patched
2. Added QUIC leak protection
3. Added QUIC DNS leak protection
4. Added IPv6 version 41/43/44/58/59/60 leak protection
5. OS version changed from HOME to PRO
6. New WebRTCMonitor tool (/tools/WebRTCMonitor.msi) Original name tcpTrigger
7. Minor bug fixes

 

[Bers666]

He has a solution too

My question was inspired by the fact many clients started alarming about QUIC who watched exactly this video.

So his solution is covered by my 2nd thing as I mentioned in the OP-post:

wait till tools like Proxifier can forward browser's UDP traffic via SOCKS5

 

[protonch]

Most sites dont use quic either so no big issue atm

Proxifier is trash as it leaks and been doing for a long time.

They can see your ip behind the proxy so they know you are masking your location

 

[Bers666]

Most sites dont use quic either so no big issue atm

atm

I asked about 2023. Man, they use QUIC for anti-bot detection, captcha, etc. You can't QUIC it is +10 to your bot score.

 

[protonch]

Well i dont know your work but for most cases i guess its fine, the only people i see complain about this issue is the people who do carding etc

 

[protonch]

And there will be a solution for the masses as companies is really good to adapt. I suggest you should contact a few services you use and have a talk about the issue and see what the response is.

 

[turelink]

I hope so
I invest too much on proxies

 

[naveenchallapalli]

what do you mean? Imagine most of them support Socks5/UDP now. But browser's can't send HTTP3 via any proxy now. So eventhough proxy providers adapted, it is useless.

double ssh tool supports

 

[Jackychans]

You can try ShadowsSock, a good resolution to relay entire UDP packets

 

[Bers666]

You can try ShadowsSock, a good resolution to relay entire UDP packets

I prefer v2rayng, ss is too simple

 

[BetterKnow]

The same exact thing was said 10 years ago when Passive OS Fingerprinting came out, yet today it's completely irrelevant. Proxying UDP/QUIC should be easy for any professional technology provider.

 

[proxygo]

i doubt its going away anytime soon - fear mongery nothing more

 

[lfdeprince]

This is already possible with Socks5h!

Hi, there is a concern about raising usage of QUIC protocol (HTTP 3.0) with combination of using a proxy in browser. QUIC is UDP. All modern browsers do support QUIC. Yet none of them support sending QUIC via a proxy. Even if the proxy itself can send UDP (most Socks5 proxies can't but some can!).

And when a website finds out you have a modern browser and can't send QUIC, it's a big red flag to consider you are a bot!

3rd party solutions like Proxifier don't support sending QUIC either.

Possible solutions:

- wait till browsers can send QUIC via a proxy + proxy providers start adding UDP to their proxies
- wait till tools like Proxifier can forward browser's UDP traffic via SOCKS5
- switch to 4G\5G VPN which are way more expensive.

This is already possible with Socks5h!

 

[aticharles]

This is already possible with Socks5h!

This is already possible with Socks5h!

where to get socks5h and what exactly is socks5h..socks5 w udp support?

The same exact thing was said 10 years ago when Passive OS Fingerprinting came out, yet today it's completely irrelevant. Proxying UDP/QUIC should be easy for any professional technology provider.

yet 9 out of 10 proxy providers sell TCP proxies only

wait till tools like Proxifier can forward browser's UDP traffic via SOCKS5

Less likely we will see tools forwarding udp packets via tcp, more likely we will see flow of UDP based proxies(VPNs) on the market

Most sites dont use quic either so no big issue atm

Proxifier is trash as it leaks and been doing for a long time.

They can see your ip behind the proxy so they know you are masking your location

yes no QUIC problem as of now, What tool would you suggest to proxify entire windows via standard socks5?

He has a solution too

Changelog:
1. New Edge 107/108 Patched
2. Added QUIC leak protection
3. Added QUIC DNS leak protection
4. Added IPv6 version 41/43/44/58/59/60 leak protection
5. OS version changed from HOME to PRO
6. New WebRTCMonitor tool (/tools/WebRTCMonitor.msi) Original name tcpTrigger
7. Minor bug fixes

These are not solution, It is just he has blocked UDP ports on firewall that communicates for QUIC DNS resolution. Blokcing is not a solution

 

[Bers666]

standard socks5

Standard Socks5 does support UDP since its beginning -- RFC1928 , March 1996.
The issue are
- Socks5 clients that don't support it and don't plan adding support of it.
- Socks5 proxy "farmers" that neglect UDP.

 

[Kontala]

Just realized my proxy provider is shit. Ordered 6 fiber connections and 3 mobile phones to run 6 mobile connections.

So 12 simultaneous rotating proxies is enough for low scale botting.

Thread solved and is subject to closing.

 

[klique]

Just realized my proxy provider is shit. Ordered 6 fiber connections and 3 mobile phones to run 6 mobile connections.

So 12 simultaneous rotating proxies is enough for low scale botting.

Thread solved and is subject to closing.

What are you talking about? How does this relate to the OP?