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

Use the current environment in forked process, so installing extension works in sandboxed environment #79

Merged
merged 1 commit into from
Jan 16, 2025

Conversation

dex4er
Copy link
Collaborator

@dex4er dex4er commented Jan 16, 2025

Fixes #77

@dex4er dex4er self-assigned this Jan 16, 2025
@dex4er dex4er added the bug Something isn't working label Jan 16, 2025
@dex4er dex4er added this to the v0.1.2 milestone Jan 16, 2025
@dex4er dex4er merged commit b3eec2b into main Jan 16, 2025
15 checks passed
@dex4er dex4er deleted the bug/fork-with-default-env branch January 16, 2025 21:50
@dex4er
Copy link
Collaborator Author

dex4er commented Jan 16, 2025

Potentially it might be risky to install an unknown extension which can steal some environment variables (authorization tokens, other secrets) however I see more use cases when environment variables are really needed: proxy server, license, location with tmpdir or cache, etc. Also snap or flatpack would need to set extra envvars for sure.

@dex4er dex4er changed the title Use the current environment in forked process Use the current environment in forked process, so installing extension works in sandboxed environment Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Installing extension fails if forked binary needs any environment variable
1 participant