Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Socks5 support #2081

Open
rustdesk opened this issue Jan 1, 2024 · 3 comments
Open

Socks5 support #2081

rustdesk opened this issue Jan 1, 2024 · 3 comments
Labels
enhancement New feature or request provider size/medium

Comments

@rustdesk
Copy link

rustdesk commented Jan 1, 2024 •
edited

Is it possible to add Socks5 proxy support?
@camshaft
Copy link
Contributor

camshaft commented Jan 1, 2024

I'm not sure I follow what the ask is. You'll have to be more specific about what functionality you're looking for. Are you wanting a QUIC-based SOCKS server? Or are you wanting s2n-quic to implement the SOCKS5 client wire protocol?

@rustdesk
Copy link
Author

rustdesk commented Jan 2, 2024 •
edited

I meant the latter, hope there is an API so that we can configure socks5 proxy for the client. Sorry for the confusion.

@camshaft
Copy link
Contributor

camshaft commented Jan 3, 2024

At this point we don't really have anything to support that use case. That being said, I wouldn't be opposed to adding some general functionality for constructing custom packet encapsulation headers to the library. This would need to be a new provider that is called at the beginning of every packet to write the header. This would provide flexibility for a wide variety of encapsulation methods, rather than just SOCKS5.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request provider size/medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@camshaft @rustdesk