Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I'm amazed I get -1 for that post; scp is clunky as hell when you already have a shell in 'that' directory; and it'll only work if you have /direct/ access to the machine you are logged in, and that's rarely the case if you first connect to a front end machine.

I did not downvote you, but setting up a port forward (-L) or SOCKS proxy (-D) on the first machine is very easy and extremely flexible. I do it all the time.

You can also do some tricks in ssh_config to route through the first machine (this is non-obvious, I'll grant). I do "ssh <secondmachine.whatever.tld>.<hopmachine>", and then I transparently connect from my workstation to the secondmachine, through the hopmachine. This is also more secure as the hop machine is just a dumb transport for data.

> I'm an embedded dev as well, and I use zmodem everyday. I have boards that have no network, just a serial port, and I can upload an executable, download the log from just the debug console.

Absolutely, zmodem is still very useful for serial links, and they are very common in embedded devices.

I really doubt there's any reason to use zmodem over SSH other than convenience if you happen to know it better than the alternatives.



> I really doubt there's any reason to use zmodem over SSH other than convenience if you happen to know it better than the alternatives.

You might not have encountered it.

Here's the use case: the ssh session terminates at a bastion host running a restricted sshd that drops port forwards and punts the connection to an internal landing host which is not permitted to ssh out.

Using an in-band file transfer protocol is incredibly useful.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: