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.

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

Connecting to target should be asynchrynous #107

Open
morganava opened this issue Jan 24, 2024 · 0 comments
Open

Connecting to target should be asynchrynous #107

morganava opened this issue Jan 24, 2024 · 0 comments
Labels
feature New feature or enhancement gosling gosling crate issue

Comments

@morganava
Copy link
Collaborator

Different from optimistic socks!

The current implementation synchronously connects to remote onion services, which blocks forward progress as tor tries to look up and connect to the onion service through the tor network.

This bottleneck prevents forward progress in the gosling handshakes. We should write our own SOCKS5 client implementation that integrates well with the gosling/torprovider event loops.

@morganava morganava added the feature New feature or enhancement label Jan 24, 2024
@morganava morganava changed the title Connecting to onion service should be asynchrynous Connecting to target should be asynchrynous Jul 5, 2024
@morganava morganava added the gosling gosling crate issue label Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or enhancement gosling gosling crate issue
Projects
None yet
Development

No branches or pull requests

1 participant