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

A configuration option to ignore injecting SSH Wrapper for certain connections/domains #4917

Open
1 task done
brezanac opened this issue May 14, 2024 · 2 comments
Open
1 task done
Labels
Feature requests Feature Requests

Comments

@brezanac
Copy link

Dupe Check

Describe the solution you'd like?

Would it be possible to add a configuration option to Warp which would allow specifying connections or domains for which the SSH Wrapper will not be injected into the connection?

Possibly something like an ignore list which Warp would check before trying to execute the SSH Wrapper script on the remote machine?

Is your feature request related to a problem? Please describe.

Currently it is only possible to either have the SSH Wrapper functionality enabled or disabled in Warp.

When SSH Wrapper is enabled it will cause connection issues if the remote server does not allow exec system calls.

warp

This is especially inconvenient when accessing enterprise-grade configurations (PaaS, SaaS) which have very strict connection rules.

Additional context

No response

How important is this feature to you?

3

Warp Internal (ignore) - linear-label:39cc6478-1249-4ee7-950b-c428edfeecd1

None

@brezanac brezanac added the Feature requests Feature Requests label May 14, 2024
@dannyneira
Copy link
Member

Thanks for this feature request @brezanac I see how this could help with those strict servers with connection limits, etc. As a stopgap, you can use the command ssh to connect instead, bypassing the ssh wrapper (make sure you don't "Warpify" the subshell).

CleanShot 2024-05-14 at 16 49 50

To anyone else interested in this feature, please add a 👍 to the original post at the top to signal that you want this feature, and subscribe if you'd like to be notified.

@brezanac
Copy link
Author

Thanks for this feature request @brezanac I see how this could help with those strict servers with connection limits, etc. As a stopgap, you can use the command ssh to connect instead, bypassing the ssh wrapper (make sure you don't "Warpify" the subshell).

While command ssh might seem like a decent enough solution it unfortunately comes with two big caveats:

  • it supresses access to shell function lookup for all functions, not just the ones related to Warp
  • it adds to the mental overhead of having to remember which connections require dropping the SSH Wrapper

Here's to hope that more people find this feature potentially useful and vote for it.

Peace and long life 🖖

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature requests Feature Requests
Projects
None yet
Development

No branches or pull requests

2 participants