Last active
June 21, 2024 14:46
-
-
Save ttscoff/ee50738f7a1605dd4f81a3e8ca74dc6e to your computer and use it in GitHub Desktop.
SOLVED: SSH issue
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| debug1: Remote: /Users/ttscoff/.ssh/authorized_keys:11: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding | |
| debug1: Remote: /Users/ttscoff/.ssh/authorized_keys:11: key options: agent-forwarding port-forwarding pty user-rc x11-forwarding | |
| debug1: Sending command: ls |
This is affecting scp and rsync as well, assuming the same root issue.
And it's not network-related, running the same command with my Synology as the target works as expected. Something about the way ssh is handling remote connections...
SOLVED
Solved, it was a problem with my config.fish.
The problem line was:
[ -f $HOMEBREW_PREFIX/share/forgit/forgit.plugin.fish ]; and source $HOMEBREW_PREFIX/share/forgit/forgit.plugin.fish
Changing to:
if status is-interactive
[ -f $HOMEBREW_PREFIX/share/forgit/forgit.plugin.fish ]; and source $HOMEBREW_PREFIX/share/forgit/forgit.plugin.fish
end
Fixed it. Thanks for all the suggestions.
Solution indirectly discovered by way of this SO post
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With command
ssh g 'ls', withgbeing the same machine (same issue usinglocalhost). It just hangs indefinitely at this point. Same with another machine on the same network. Same command works fine with remote linux machines. WTF.