41–50 of 102 posts
I'm here to answer questions anyone has about this. It's a newish feature so feedback is welcome, and bug reports are greatly appreciated. Also, credit goes to FinalTerm for the inspiration. RIP.
How should we think about the security story when sshing from a more trusted to a less trusted host?
I'd love to use a terminal with similar features on linux
I'm concerned about the wget to an external server part. This file should be local to prevent excessive slowness and potential security issues. Also, is there a zsh version of this file? zsh is extremely popular on osx.
The linked page explains how to install by hand. I'd like to eliminate the curl|bash. It's tricky to deploy a shell script in a terminal emulator, so it hasn't been done yet. The ability to fix bugs without making users upgrade their client has been invaluable during early beta.
Earlier quoted context omitted.
Except that it doesn't shell out, so it ignores ProxyCommand...
What do you use ProxyCommand for? It seems hard to support, but I'd like to know more.
I'm here to answer questions anyone has about this. It's a newish feature so feedback is welcome, and bug reports are greatly appreciated. Also, credit goes to FinalTerm for the inspiration. RIP.
Thanks for your hard work and generosity. How should we think about the security story when sshing from a more trusted to a less trusted host?
When installing, especially on an untrusted host, follow the manual installation instructions. The menu item will just output a curl|bash command (currently; this will likely change in the future).
If the host is really untrusted you're screwed, of course. Bad guys could modify your ~/.iterm2_shell_integration.bash and you'd never know. But this script is not special in any way (except that it's kinda complex and is run automatically). Maybe hash it from time to time if you're really paranoid.
The scripts assume that various things in your path are safe to run. printf, hostname, sed, echo, etc. If those are compromised you're in a bad way, and I don't think shell integration exposes anything that ordinary use wouldn't.
If you've been compromised badly enough that an attacker can decrypt your ssh session, your current directory will be revealed at each prompt. But it probably is since most people have that in their $PS1 anyway. Also the host's idea of its fully-qualified domain name.
Probably the most risky aspect of shell integration is the secure copy feature. It's possible that there's a bug in my use of libssh2 or that there are unpatched vulnerabilities in an out-of-date build of iTerm2 (or an up-to-date version of iTerm2 with an out-of-date libssh2). I try to stay on top of changes to libssh2 but I am human and Sparkle (the auto-updater) is not flawless either.
That's all that comes to mind. I'm sure other folks on here can think of more interesting attacks or vulnerabilities.
Earlier quoted context omitted.
Except that it doesn't shell out, so it ignores ProxyCommand...
What do you use ProxyCommand for? It seems hard to support, but I'd like to know more.
Earlier quoted context omitted.
The linked page explains how to install by hand. I'd like to eliminate the curl|bash. It's tricky to deploy a shell script in a terminal emulator, so it hasn't been done yet. The ability to fix bugs without making users upgrade their client has been invaluable during early beta.
Would it be possible for iTerm to "type" the whole thing in for me? It's already executing a curl, can it do the whole thing through the host?
Earlier quoted context omitted.
The linked page explains how to install by hand. I'd like to eliminate the curl|bash. It's tricky to deploy a shell script in a terminal emulator, so it hasn't been done yet. The ability to fix bugs without making users upgrade their client has been invaluable during early beta.
Well, if all I have to do is run the script, I can just import it into my git repo (by submoduling iterm2's git repo, if they have one; if they don't, they need one just for this script), and just call it normally (with a bit of if wrapper to not execute on non-iterm2 terms).
Earlier quoted context omitted.
What do you use ProxyCommand for? It seems hard to support, but I'd like to know more.
I also use a smartcard with gpg-agent speaking the ssh-agent protocol. OpenSSH commandline supports it fine. What's the harm in shelling out?
Earlier quoted context omitted.
I've used it in the past to ssh via bastion hosts and the like.
Yes. My config is something like this: # proxy n02 connections through bastion host n02.university.edu ProxyCommand ssh bastion.university.edu -W %h:%p 2> /dev/null Almost all my remote shells require a similar setup.