Restore backup via SSH Multiple accounts

[Patricia-USA]

I want to manipulate the daemon (run, stop, reload the configuration ...), we use the command
/ Etc / init.d / ssh
The configuration file of the SSH server is / etc / ssh / sshd_config. Not to be confused with / etc / ssh / ssh_config file is the configuration of SSH client. After that i want to back up via SSH Multiple accounts. Please help. Thanks in advance.

[MindSpace]

Among the many options you may note:

* Port 22: Means that the SSH server listening on port 22, which is the normal SSH port. It is possible to listen on another port by changing this line.
* Protocol 2: Means that the SSH server only accepts version 2 of the SSH protocol. It is a more secure version than the version 1 protocol. To accept the two protocols, change the line: Protocol 2.1
* PermitRootLogin No: Means that you can not login as root via SSH. To log in as root, simply login as normal user and use su.
* X11Forwarding yes: Authorizes the transfer by SSH graphical display.
* LoginGraceTime 600: Maximum connection time.

[Zecho]

You need to two types of authentication are possible: password and key. In both cases we use one of the following:
ssh-server <login> <IP SSH>
<login> @ ssh server <IP SSH>
[change] Authentication password
This is the easiest method. Upon connection, the ssh client requests the password of the account. In this case, ssh encrypts the password that prevents movement in clear view on the network.

[opaper]

SSH is also able to provide encryption to other services (eg ftp) via the port forwarding. (Options-L and-R command ssh), as follows:
Consider two stations host1 and host2. Suppose that the machine host1, you use the command:
ssh-L p1: host2: p2 host2
or host2:
ssh-R p1: host2: host1 p2
then you get a secure tunnel in which you can pass any connection, which will be automatically encrypted.
On host1, ssh-L p1: host2: p2 host2 means that when connecting to port p1, the packets are transmitted to the port P2 of the machine via host2 host2.

[Reegan]

The command requires a filename to save the private key and a filename to save the public key. By default, the private key is stored in the file $ HOME / .ssh / id_dsa. The private key is saved with permissions 600. The public key has the same file name followed by ". Pub", with permissions 644. When creating the key, the utility requires pass phrase which is a password to protect the private key (2nd Protection). The pass phrase used to encrypt the private key. The pass phrase is then applied to each use of the private key, ie every time you log in using this method of authentication. A mechanism called ssh-agent can not enter the password each time. It is possible to change the pass phrase that protects private key with the command ssh-keygen-p.

[Osman84]

To allow a key to connect to an account, you must place the public share in the file $ HOME / .ssh / authorized_keys the account in question, the SSH server. If you want to connect to the server on behalf sasa, the file is / home / sasa / .ssh / authorized_keys. To transfer the public key, you can use ftp, scp (ssh copy file), or a simple copy / paste between two terminals (it's just a long line of ASCII characters).

[Kanakpriya]

If you are brought to you connect to both a gateway and a machine behind the bridge (the latter being a port forwarding between, for example, port 2222 and port 22 of the internal machine), you'll encounter a problem. Indeed, the first time you connect to an SSH machine, your SSH client associates (in encrypted form) its IP with the public key of the host machine contacted but not with the number port (File ~ / .ssh / Known_hosts). When you connect to the machine internally by port 2222 of the gateway (ssh -P 2222 bridge), The SSH client will register the IP gateway associated with the host key the internal machine. If you then connect directly to the bridge on its port 22, you will get an error message saying that the host key has changed and you could not connect.