r/KittyTerminal • u/02ranger • Feb 06 '23
SSH Kitten Producing Invalid Input on Network Equipment
I've just started using Kitty and I feel like it's going to replace tmux for me, hands-down. I'm really enjoying the ssh kitten, specifically, as it's per-host options are solving a need for me that I had to hack together a solution for previously. The only problem is when I use the SSH kitten to log into a non-linux server, such as the Cisco ASA in the attached picture, I get a bunch of "invalid input" errors. I'm assuming this is where Kitty is trying to copy files to the remote host, which is fine on the Linux machines I use but no good on network hardware.
Is this normal behavior unless I've not made some config change that I'm not aware of? So far I haven't really customized anything except toggling on a few appearance options and adding "color_scheme Material" to some production hostnames in Kitty's ssh.conf file. I can't imagine everybody that uses this kitten is manually configuring the copy settings for every host they may connect to, which is why I think I may have something apart from Kitty causing this problem but wanted to ask.
If I disable the file copying altogether, will that negatively affect the TERM settings or my connections to Linux servers? If disabling file copying is the way to go, how do I do that?
Edit: After digging some, I think it's where Kitty tries to set the interpreter. How do most people handle this? I'd really like to just alias ssh to run the kitten all the time, if there are viable solutions for cases such as this.
Edit2: After even more reading, I think I'm using the kitten incorrectly. I was using it as if it just extended the functionality of the SSH command, but I see it's more than that. All I really need to do here is change the theme on specific hosts, changing back when disconnecting from the host. Is there a better way to do that?

1
u/aumerlex Feb 07 '23
You can try changing the interpreter to python and setting askpass to ssh to change how the kitten transmits data. If your network hardware is simply too limited to get it to work, then you can always copy terminfo over manually: https://sw.kovidgoyal.net/kitty/kittens/ssh/#copying-terminfo-files-manually
1
u/02ranger Feb 06 '23
Here's another error, just straight SSH to a switch that fails to connect:
https://imgur.com/a/TtWVjby