Downloading with SSH

RobInRockCity · 02-24-2015, 05:28 PM

Quote:

Originally Posted by suicidaleggroll

If you're worried about it, don't use a drag and drop GUI. Do it from the command line where you're made aware of everything that happens.

If someone teaches me how to do that, I would consider it...

Don't I need "rsynch" or something like that to do that?

In fact, not to go off on a whole other topic, BUT, what is the best way for me to be backing up my VPS?

To me, I would want to do an "image" of my entire VPS, so if there were any issues, *everything* could be restored!!!

Since I have cPanel, I assume that the Backup app will do a good job at that?

(If there is a better way, I would consider it...)

Then after I back things up, can I simply use SCP, or do I need that rsynch thing or something else?

Sincerely,

Rob

RobInRockCity · 02-24-2015, 05:29 PM

Quote:

Originally Posted by Miati

Read through this to gain a understanding of the handshake of ssh.

ssh connecting or transmitting through plain-text would be against the foundation of it's design. It was designed to replace telnet which does transmit in plain-text.

Okay, I guess that makes sense...

Miati · 02-24-2015, 05:31 PM

Quote:

Originally Posted by RobInRockCity

Code:

scp hostname:file directory/

Is the reason that nothing else was needed is because SCP runs over SSH? (And if so, in my case, then I guess the whole SSH Key Authentication thing has to work, right?)

Yes - exactly.

From scp man page

Code:

scp copies files between hosts on a network.  It uses ssh(1) for data
     transfer, and uses the same authentication and provides the same security
     as ssh(1).  scp will ask for passwords or passphrases if they are needed
     for authentication.

Whatever it takes to login via ssh, will be the same for scp.

Any passwords will be asked after the command is run and if pub based key auth is used (with ssh-agent which securely stores credentials) no password is needed.

Yes, the link is stuffy, but you're asking about details of how ssh works. Take the time to read and understand it (and find other resources (man ssh perhaps) if it's not enough). If there is a part you don't get - feel free to ask about it

-----

rsync (not rsynch) is a method of backing up. It's designed to be a efficent method of making sure two directories are the same. It can actually use the ssh backend as well (that seems to occur a lot)
scp is another method.
in terminal, there are often multiple good solutions to everything. Unlike gui's, much of what is written in cli is meant to do one thing, and to do it well.

Quote:

If someone teaches me how to do that, I would consider it...

A lot of the information you want is on the web already, probably written in a manner far better then possibly written here. use the man pages and search engines to figure out the best method.

RobInRockCity · 02-24-2015, 05:37 PM

Quote:

Originally Posted by Miati

From scp man page

Code:

scp copies files between hosts on a network.  It uses ssh(1) for data
     transfer, and uses the same authentication and provides the same security
     as ssh(1).  scp will ask for passwords or passphrases if they are needed
     for authentication.

Whatever it takes to login via ssh, will be the same for scp.

I have heard that SSH-1 is outdated and insecure...

Why not SSH-2?

Quote:

Originally Posted by Miati

Yes, the link is stuffy, but you're asking about details of how ssh works. Take the time to read and understand it (and find other resources (man ssh perhaps) if it's not enough). If there is a part you don't get - feel free to ask about it

I'm trying to learn all of this as fast as I can. I just have an enormous amount on my plate - like getting a running website!!

Learning is coming in bits and pieces in between.

Thanks,

Rob

Miati · 02-24-2015, 05:39 PM

Quote:

I have heard that SSH-1 is outdated and insecure...

Why not SSH-2?

This is from the man page, the (1) references to pages in the man page.

SSH-1 is indeed very insecure. Usage is not a good idea.

suicidaleggroll · 02-24-2015, 05:51 PM

Quote:

Originally Posted by RobInRockCity

I have heard that SSH-1 is outdated and insecure...

Why not SSH-2?

The (1) refers to section 1 in the manual.
If you type "man 1 ssh" (or just "man ssh"), at the top you'll see SSH(1)

ssh only has one section in the manual that I'm aware of, but for comparison see:
man 1 printf
vs
man 3 printf

RobInRockCity · 02-24-2015, 05:58 PM

Is there a way for me to confirm that my installation is running SSH-2?

And is there a way for me to see if SSH-1 is turned off?

My VPS runs CentOS 6, and I do not currently have Root access.

Thanks,

Rob

suicidaleggroll · 02-24-2015, 06:02 PM

Use the -v flag in your ssh command.

You can disabled v1 by editing /etc/ssh/ssh_config on your local machine and forcing Protocol to 2.