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

Custom blocklist blocks VS Code #1600

Closed
touhidurrr opened this issue Jun 27, 2024 · 2 comments
Closed

Custom blocklist blocks VS Code #1600

touhidurrr opened this issue Jun 27, 2024 · 2 comments
Labels
bug TYPE: a report on something that isn't working stale ATTRIBUTE: this issue has not had recent activity

Comments

@touhidurrr
Copy link

touhidurrr commented Jun 27, 2024

Pre-Submit Checklist:

What happened:

A rule in my custom blocklist v0cdn.net blocked extentions download and info page because a subdomain of vassets.io happened to be a CNAME of a subdomain of v0cdn.net.

Later an allow rule for .vassets.io fixed this.

What did you expect to happen?:

I was not expecting the block to be this strong and break extensions manager in VS Code.

How did you reproduce it?:

Add one rule in your custom blocklist v0cdn.net and try to install / update any extension from VS Code extensions store.

What do I expect the maintainer to do?

I noticed that some apps have default configs injected by PortMaster. VS Code can have a default config allow rule .vassets.io so that users do not have to face the same issue in future.

@touhidurrr touhidurrr added the bug TYPE: a report on something that isn't working label Jun 27, 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.

Copy link

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 Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug TYPE: a report on something that isn't working stale ATTRIBUTE: this issue has not had recent activity
Projects
None yet
Development

No branches or pull requests

1 participant