SSH-tools: Making SSH more convenient
github.com
SSH-tools: Making SSH more convenient
1–10 of 37 posts
Re: SSH-tools: Making SSH more convenient
#2One thing I wish ssh would make easier is terminfo. I have moved from using xterm as my daily terminal emulator to kitty. The only complaint I have is when I ssh around, I need to copy the terminfo to the remote system (kitty does not use TERM="xterm-256color" because it is not 100% compatible).
Kitty does have a ssh wrapper which can copy the terminfo for me, but I rarely remember to use it. And it doesn't work for every scenario. Honestly, I wish that it was more common / feasible to probe terminals for capabilities instead of relying on an env var & terminfo files.
So while I wait for the kitty terminfo to be in the database by default on most systems, I often override TERM to xterm-256color.
Re: SSH-tools: Making SSH more convenient
#3Looks very handy. Thanks for these tools!
Re: SSH-tools: Making SSH more convenient
#4One thing I wish ssh would make easier is terminfo. I have moved from using xterm as my daily terminal emulator to kitty. The only complaint I have is when I ssh around, I need to copy the terminfo to the remote system (kitty does not use TERM="xterm-256color" because it is not 100% compatible). Kitty does have a ssh wrapper which can copy the terminfo for me, but I rarely remember to use it. And it doesn't work for…
I solved this issue by adding
alias ssh='TERM=xterm-256color ssh'
Re: SSH-tools: Making SSH more convenient
#5One thing I wish ssh would make easier is terminfo. I have moved from using xterm as my daily terminal emulator to kitty. The only complaint I have is when I ssh around, I need to copy the terminfo to the remote system (kitty does not use TERM="xterm-256color" because it is not 100% compatible). Kitty does have a ssh wrapper which can copy the terminfo for me, but I rarely remember to use it. And it doesn't work for…
Modern ssh clients support adding a "SetEnv" in .ssh/config, might work for overriding TERM as well
Re: SSH-tools: Making SSH more convenient
#6One thing I wish ssh would make easier is terminfo. I have moved from using xterm as my daily terminal emulator to kitty. The only complaint I have is when I ssh around, I need to copy the terminfo to the remote system (kitty does not use TERM="xterm-256color" because it is not 100% compatible). Kitty does have a ssh wrapper which can copy the terminfo for me, but I rarely remember to use it. And it doesn't work for…
Fellow Kitty user here, similar hurdles.
If you haven't implemented it in your workflow already, you can conditionally set TERM for hosts in your SSH configs with SetEnv.
This is one of the few, if not the only, variable that SSHd will allow clients to set for free.
Re: SSH-tools: Making SSH more convenient
#7Learning a little vim (i.e. how to open multiple buffers and tabbing between them) as well as learning a little tmux and a little htop has made my experience with ssh way more palatable.
Re: SSH-tools: Making SSH more convenient
#8Anyone knows a way to use vault cert auth with proxycommand or something like that? To use it transparently with emacs and other tools.
Re: SSH-tools: Making SSH more convenient
#9One thing I wish ssh would make easier is terminfo. I have moved from using xterm as my daily terminal emulator to kitty. The only complaint I have is when I ssh around, I need to copy the terminfo to the remote system (kitty does not use TERM="xterm-256color" because it is not 100% compatible). Kitty does have a ssh wrapper which can copy the terminfo for me, but I rarely remember to use it. And it doesn't work for…
Fellow Kitty user here, similar hurdles. If you haven't implemented it in your workflow already, you can conditionally set TERM for hosts in your SSH configs with SetEnv. This is one of the few, if not the only, variable that SSHd will allow clients to set for free.
What does your last sentence mean? What is the "cost" for setting other vars?
Re: SSH-tools: Making SSH more convenient
#10Earlier quoted context omitted.
Fellow Kitty user here, similar hurdles. If you haven't implemented it in your workflow already, you can conditionally set TERM for hosts in your SSH configs with SetEnv. This is one of the few, if not the only, variable that SSHd will allow clients to set for free.
What does your last sentence mean? What is the "cost" for setting other vars?
It means it's not constrained by security concerns. Some Env are not forwarded. This one is.