Skip to content

Load env vars from login shell in remote server - #40148

Merged
maxbrunsfeld merged 1 commit into
mainfrom
remote-env-vars-for-node
Oct 13, 2025
Merged

Load env vars from login shell in remote server#40148
maxbrunsfeld merged 1 commit into
mainfrom
remote-env-vars-for-node

Conversation

@maxbrunsfeld

Copy link
Copy Markdown
Collaborator

Fixes a bug mentioned in #38891

Release Notes:

  • Fixed a bug where environment variables like NODE_EXTRA_CA_CERTS were not loaded from the user's shell initialization scripts in WSL or SSH remote projects.

Co-authored-by: Cole Miller <cole@zed.dev>
@cla-bot cla-bot Bot added the cla-signed The user has signed the Contributor License Agreement label Oct 13, 2025
@zed-industries-bot

Copy link
Copy Markdown
Contributor
Messages
📖

This PR includes links to the following GitHub Issues: #38891
If this PR aims to close an issue, please include a Closes #ISSUE line at the top of the PR body.

Generated by 🚫 dangerJS against b6db568

@cavebatsofware

Copy link
Copy Markdown
Contributor

I think it would be good to advise the user that the application is loading local env vars to the server as that is not necessarily expected and may not be considered secure in some environments.

@maxbrunsfeld

Copy link
Copy Markdown
Collaborator Author

Can you say more about how this is not considered secure? I don't think we're doing anything unusual here - the environment variables never leave the remote machine.

@maxbrunsfeld
maxbrunsfeld merged commit 6a2bad4 into main Oct 13, 2025
23 checks passed
@maxbrunsfeld
maxbrunsfeld deleted the remote-env-vars-for-node branch October 13, 2025 23:09
maxbrunsfeld added a commit that referenced this pull request Oct 13, 2025
Fixes a bug mentioned in
#38891

Release Notes:

- Fixed a bug where environment variables like `NODE_EXTRA_CA_CERTS`
were not loaded from the user's shell initialization scripts in WSL or
SSH remote projects.

Co-authored-by: Cole Miller <cole@zed.dev>
@cavebatsofware

Copy link
Copy Markdown
Contributor

Can you say more about how this is not considered secure? I don't think we're doing anything unusual here - the environment variables never leave the remote machine.

I don't think its necessarily insecure, other than than users may not realize its being done. Its a good change imo. Just seems like its a human vector. Not an application issue.

@cavebatsofware

Copy link
Copy Markdown
Contributor

Contracting I sometimes connect to machines that I don't necessarily trust, but I don't do the eval with zed. I do it with traditional tools. But I could see others doing this with less awareness.
]

@cavebatsofware

Copy link
Copy Markdown
Contributor

@maxbrunsfeld Responded but just for clarity ^^

jolutz pushed a commit to jolutz/zed that referenced this pull request Aug 8, 2026
Fixes a bug mentioned in
zed-industries#38891

Release Notes:

- Fixed a bug where environment variables like `NODE_EXTRA_CA_CERTS`
were not loaded from the user's shell initialization scripts in WSL or
SSH remote projects.

Co-authored-by: Cole Miller <cole@zed.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed The user has signed the Contributor License Agreement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants