Download file during ssh session

If you are needing to sudo or su to get to this file on the remote system, the proper thing to do is copy it to your normal user's home directory, chmod so your normal user owns and can read it, then get it with scp , etc. If the file is very large, chmod the file directly temporarily without making a copy. Another thing you can try - If you are running your own SSH server at home or wherever, and it's reachable from the remote SSH server you're logged into, you can use scp to send it from your remote session to your local system.

The way I would do what you're asking for would be to turn on session logging on your ssh client Ways to do this vary. Depending on the file you might get away with just setting a big scrollback buffer.

You can then trim the extraneous bits off of either end of the log and base64 decode it back into your original file.

Some client programs have methods built in for doing pretty much the same thing with, say, the XMODEM protocol or similar, but availability of the transmission software on the server side is probably going to be a lot less than for base64, which is included in most of the Linux distros I've used recently. If you have a client that supports it though, it takes care of the chopping and decoding phase automatically, which can be convenient for large files.

I don't know that anybody's really used it since the days of telnet BBSs though, so good luck. The basic format of the command is as follows:. The biggest kicker is how to format the remote part. When you address a remote file, you need to do it in the following manner:. This is followed by a colon, then the path to the file or folder in question.

This allows me to specify a port number instead of the default Secure copy is great. You can put it in scripts and have it do backups to remote computers. The problem is that you may not always be around to enter the password. Well, we can get around using passwords by using key files.

I use this with cygwin for instance. The only problem is that this requires installing xclip if you don't already have it. Oh, and this works with binary files too. One of the many reasons we use SecureCRT — despite preferring open source software where practical — is the ease of doing file transfers. The easiest to use is ZModem. When you type something like sz file-to-download on the remote command line, the remote sz program writes out an escape sequence that tells SecureCRT to immediately start downloading file-to-download to the default download directory.

A nice touch is that the download directory is customizable per session. We use this to have per-site directories on our main office file server, so we don't have to manually sort downloaded files. It is packaged for most Unixy systems already. If for some reason your remote system doesn't have it installed already, and you can't easily install a binary package, the source package is small and highly portable.

More than once, I've had to send an lrzsz 'sharchive' or uuencode 'd tarball to a stripped-down remote system so I could ZModem files to it.

By 'tightly integrated,' I mean that when you give the SFTP menu command or keyboard shortcut, it opens a new tab connected to the remote site over the same SSH connection.

Thus, you don't need to log back in, and the connection is established a bit faster than if you had opened a separate SFTP connection to the same server. Thus, retrieving a remote file called somefile. Drag-and-drop - If you drag-and-drop a file onto the terminal window, it automatically types rz for you and starts sending the file. Thus, sending a file to a remote system could be as simple as Alt-P , drag , drop. ZModem was designed in the days when a 64 kiB block size was considered 'large.

One nice thing about the drag-and-drop mode of operation is that it takes one of the stresses out of using ZModem. When you type rz at the remote system, SecureCRT pops up a file picker automatically. You then have about a minute to find and select the file before the remote side times out.

This creates a race-against-the-clock vibe that isn't pleasant. Drag-and-drop lets you find the file at your leisure, then start the transfer with a single quick motion of the mouse. We do still use the manual method, starting the transfer with an explicit rz command. Windows 10 already has SCP installed by default. The color contrasts with the yellow, and syntax highlighting is a nice change from the drab command line.

As you can see, you first need to confirm the connection using the RSA fingerprint of the remote server. Replace [UserName] with your own Windows username. Each RSA fingerprint is added on a new line. This allows you to clear them easily by deleting an entire line at once if you ever need to remove an entry.

Navigate to the location you specified in your SCP command and the file should be visible. SCP is the most direct way to transfer files from remote servers to local systems. It makes use of the same SSH protocols, so the connection is encrypted all the way through, making it immune to man-in-the-middle attacks.

Hopefully, this tutorial will help you use it in an efficient, and easy manner.