Skip to content
This repository has been archived by the owner on Jan 4, 2019. It is now read-only.

SOCKS5 authentication support #462

Closed
riastradh-brave opened this issue Jan 30, 2018 · 1 comment
Closed

SOCKS5 authentication support #462

riastradh-brave opened this issue Jan 30, 2018 · 1 comment
Assignees

Comments

@riastradh-brave
Copy link
Contributor

In order to isolate circuits for different sessions and first-party origins, we need to specify a distinct username/password pair for each isolation domain when making requests to the tor socks proxy.

Draft is currently in progress here: https://github.com/riastradh-brave/muon/tree/riastradh-socks5-auth

@riastradh-brave
Copy link
Contributor Author

This will require some work to rebase on top of Chromium 64, since I did the initial work on Chromium 63 before we updated to 64!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant