Open brezanac opened 1 month ago
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).
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.
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:
Here's to hope that more people find this feature potentially useful and vote for it.
Peace and long life 🖖
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.
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