ssh_key_help
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ssh_key_help [2014/02/21 17:15] – bguillon | ssh_key_help [2016/12/12 10:24] (current) – [Windows] onicolas | ||
---|---|---|---|
Line 1: | Line 1: | ||
# SSH key creation procedure | # SSH key creation procedure | ||
- | This little guide is there to help you with the creation of your SSH key. This key will then be used for SSH connection | + | This little guide is there to help you with the creation of your SSH key. This key will then be used for SSH connections |
## Unix | ## Unix | ||
The SSH key generation is fairly straightforward on Unix systems: | The SSH key generation is fairly straightforward on Unix systems: | ||
- | `you@yourpc: | + | < |
+ | you@yourpc: | ||
+ | </ | ||
- | Replace | + | The part in braces '[ ]' is optional and omitting it will generate key files at the default location ($HOME/ |
- | Two files will be created | + | |
1. The public key will have the *.pub* extension. This **is** the key that you will send us. | 1. The public key will have the *.pub* extension. This **is** the key that you will send us. | ||
2. The private key should **never** be sent to anyone, even us, and remain secret. | 2. The private key should **never** be sent to anyone, even us, and remain secret. | ||
- | You can get more info about the `ssh-keygen` command in the **manpage** | + | You can get more info about the `ssh-keygen` command in the **manpage** |
## Windows | ## Windows | ||
- | The SSH key generation can be a little bit more difficult on MS Windows, | + | The SSH key generation can be a little bit more difficult on MS Windows, |
You can get Putty (the SSH client) and Puttygen (the key generation tool) from the author' | You can get Putty (the SSH client) and Puttygen (the key generation tool) from the author' | ||
Line 27: | Line 28: | ||
{{ :: | {{ :: | ||
- | You should end up with two files, a public and a private | + | You should end up with two files, a public and a private |
1. The public key will have the *.pub* extension. This **is** the key that you will send us. | 1. The public key will have the *.pub* extension. This **is** the key that you will send us. | ||
Line 34: | Line 35: | ||
If you're lost, ask Microsoft Customer Service. | If you're lost, ask Microsoft Customer Service. | ||
Just kidding, go read the [docs](http:// | Just kidding, go read the [docs](http:// | ||
+ | |||
+ | # Usage of your SSH key in CorteXlab | ||
+ | |||
+ | ## Important notice | ||
+ | |||
+ | If you are not familiar with SSH you might not be aware that the keys you just created will be needed whenever you want to connect to the testbed. That means that if you want to connect from another computer (i.e. not the one on which you generated the keys) you will have to copy both keys to this other computer. | ||
+ | |||
+ | The two files that you must copy are: | ||
+ | |||
+ | * The private key (default: `~/ | ||
+ | * The public key (default: `~/ | ||
+ | |||
+ | Remember: your SSH private key is strictly confidential and personnal. Thus, it should be handled with care when you proceed with its copying on your computers. Moreover, this is what identifies you as a CorteXlab user and you do not want those to fall into the wrong hands. | ||
+ | |||
+ | ## Having multiple SSH keys | ||
+ | |||
+ | We **do not support** users having multiple SSH keys yet. But this is definitely a feature that should be implemented in the near future. |
ssh_key_help.1392999301.txt.gz · Last modified: 2014/05/21 15:45 (external edit)