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

[Feature Request] Per-host exit node rules and per-connection circuit refresh #1474

Closed
realSaltyFish opened this issue Jan 31, 2024 · 5 comments
Labels
stale ATTRIBUTE: this issue has not had recent activity suggestion TYPE: idea for new feature or improvements

Comments

@realSaltyFish
Copy link

What would you like to add or change?:

  1. Allow setting exit node rules based on domain name. For example, users can make all a.com traffic exit from the US, while all b.com traffic exit from Australia.
  2. Allow getting a new exit node for a specific connection (e.g. Firefox's connection to a.com) on-demand.

Why do you and others need this?:
This would be very helpful for websites that implement geoblocking or IP-based risk management, which are very common.

Currently I could set global exit rules to bypass geoip restrictions, but to reduce its impact on privacy I have to switch it back each time I'm done accessing the geoblocking website. This requires a Portmaster restart and is very inefficient.

Sometimes a website denies access when it detects a public proxy IP. Each time I get IP blocked I have to re-initialize the SPN. This interrupts all established connections and brings a lot of hassle, and doesn't necessarily gets around the IP ban since there's a good chance I'll get the same exit node for the same connection. Tor allows switching to a "new circuit" on demand, and SPN should also support this.

@realSaltyFish realSaltyFish added the suggestion TYPE: idea for new feature or improvements label Jan 31, 2024
Copy link

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

  • 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
  • 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

@Raphty
Copy link
Member

Raphty commented Jan 31, 2024

Thank you for the idea!

we are thinking about where to put such settings, if you have feedback/ideas regarding this, help is welcome 😁

@realSaltyFish
Copy link
Author

Thanks for considering my request!
Exit node rules could be an addition to the existing "SPN Rules" settings section. It currently only supports "allow" and "exclude" operations and could be extended to support custom rules.
For on-demand exit node switching, I think a "new identity" button could be added to the marked position.

image

@dhaavi dhaavi transferred this issue from safing/spn Mar 29, 2024
Copy link

github-actions bot commented Jun 3, 2024

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Jun 3, 2024
Copy link

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale ATTRIBUTE: this issue has not had recent activity suggestion TYPE: idea for new feature or improvements
Projects
None yet
Development

No branches or pull requests

2 participants