This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
other:putty_conf [2023/03/16 16:09] jypeter [Adding more connection profiles] Started moving from ciclad to spirit |
other:putty_conf [2023/03/23 10:49] jypeter [Creating ssh keys with PuTTYgen] |
||
---|---|---|---|
Line 70: | Line 70: | ||
=== New profile for a direct connection to a remote server === | === New profile for a direct connection to a remote server === | ||
- | * Select an existing session (e.g. the [[#creating_a_new_session|ssh1 profile]] defined above) and click on **Load** | + | * Select an existing (and correctly configured) session (e.g. the [[#creating_a_new_session|ssh1 profile]] defined above) and click on **Load** |
* Update the values of the **Host Name** and **Saved Session** (the name of the new profile you want) text fields, and settings | * Update the values of the **Host Name** and **Saved Session** (the name of the new profile you want) text fields, and settings | ||
* Example: connecting to **LSCE from INSIDE LSCE**\\ (inside <=> computer connected to the wired network): | * Example: connecting to **LSCE from INSIDE LSCE**\\ (inside <=> computer connected to the wired network): | ||
Line 80: | Line 80: | ||
* ''Saved Session'' => ''spirit1'' | * ''Saved Session'' => ''spirit1'' | ||
* do not forget to **specify your IPSL login** in: ''Connection'' => ''Data'' => ''Auto-login username'' | * do not forget to **specify your IPSL login** in: ''Connection'' => ''Data'' => ''Auto-login username'' | ||
- | * you will also need an [[other:putty_conf#using_ssh_keys|ssh key]] if you want to connect to ''spirit'' !! | + | * you will also need an [[other:putty_conf#using_ssh_keys|ssh key]] if you want to connect to one of the IPSL ''spirit'' servers !! |
- | * Go back to ''Category'' => ''Session'' and **Save** the session | + | * Go back to ''Category'' => ''Session'' and <wrap em>**Save** the session</wrap> |
=== New profile with a connection through a gateway === | === New profile with a connection through a gateway === | ||
* Select an existing //gateway// session (e.g. ''ssh1'') and click on **Load**.\\ For connecting to LSCE **from OUTSIDE LSCE**, select the [[#creating_a_new_session|ssh1 profile]]\\ If you are at LSCE, but use the //eduroam// or the //guest// **WiFi network**, you are considered as being //outside LSCE//! | * Select an existing //gateway// session (e.g. ''ssh1'') and click on **Load**.\\ For connecting to LSCE **from OUTSIDE LSCE**, select the [[#creating_a_new_session|ssh1 profile]]\\ If you are at LSCE, but use the //eduroam// or the //guest// **WiFi network**, you are considered as being //outside LSCE//! | ||
- | * In the ''Connection'' => ''SSH'' category, specify the command used to connect to the target server in the **Remote command** field\\ e.g. **for LSCE**, use: | + | * In the ''Connection'' => ''SSH'' category, specify the command used to connect to the target server from the //gateway//, in the **Remote command** field\\ e.g. **for LSCE**, use: |
* ''ssh -X -A obelix'' (check the [[other:ssh#standard_usage|useful ssh options]] for more details on the options)\\ {{ :other:putty_10b.png?direct |}} | * ''ssh -X -A obelix'' (check the [[other:ssh#standard_usage|useful ssh options]] for more details on the options)\\ {{ :other:putty_10b.png?direct |}} | ||
- | * Go back to ''Category'' => ''Session'', <wrap hi>specify a new profile name</wrap> in **Saved Sessions** (e.g. ''obelix via ssh1'') and **Save** the session\\ {{ :other:putty_11.png?direct |}} | + | * Go back to ''Category'' => ''Session'', <wrap hi>specify a new profile name</wrap> in **Saved Sessions** (e.g. ''obelix via ssh1'') and <wrap em>**Save** the session</wrap>\\ {{ :other:putty_11.png?direct |}} |
===== Daily usage of PuTTY/Pageant ===== | ===== Daily usage of PuTTY/Pageant ===== | ||
Line 119: | Line 119: | ||
<WRAP center round alert 60%> | <WRAP center round alert 60%> | ||
- | In this section, we will use files that have the same base name, and different extensions. | + | In this section, we will use //key// files that have the same base name, and **different extensions**: e.g. ''id_ed25519'', ''id_ed25519**.pub**'' and ''id_ed25519**.ppk**'' |
You should **make sure that you can [[other:win10config#displaying_hidden_folders_and_files_and_the_files_extension|see hidden folders, and files' extensions]]** before you go further! | You should **make sure that you can [[other:win10config#displaying_hidden_folders_and_files_and_the_files_extension|see hidden folders, and files' extensions]]** before you go further! | ||
Line 125: | Line 125: | ||
- | Read the [[other:ssh#using_ssh_keys|Using ssh keys]] section if you don't know what //ssh keys// are | + | Read the [[other:ssh#using_ssh_keys|Using ssh keys]] section if you don't already know what //ssh keys// are |
<WRAP center round important 80%> | <WRAP center round important 80%> | ||
* **Do not lose** the (existing) ssh keys files you have, or the keys that you will create | * **Do not lose** the (existing) ssh keys files you have, or the keys that you will create | ||
Line 134: | Line 134: | ||
* Read [[other:ssh#some_common_sense_advice|Do not forget your passphrase!]] if you need some advice about passphrases | * Read [[other:ssh#some_common_sense_advice|Do not forget your passphrase!]] if you need some advice about passphrases | ||
- | * The best thing to do is probably to **keep the keys in the standard [[other:ssh#configuration_files|ssh configuration directory]]**! | + | * The best thing to do is probably to **store the //key// files in the standard [[other:ssh#configuration_files|ssh configuration directory]]** of each desktop/laptop/servers you use! |
</WRAP> | </WRAP> | ||
==== Converting existing ssh keys with PuTTYgen ==== | ==== Converting existing ssh keys with PuTTYgen ==== | ||
Line 166: | Line 166: | ||
* Make sure that the selected //Type of key to generate// (at the bottom of the ''PuTTYgen'' window) is ''EdDSA'' (short for //Edwards-curve DSA//), with the default ''255'' bits.\\ This will generate **//ed25519// keys** that are now recommended on the IPSL servers | * Make sure that the selected //Type of key to generate// (at the bottom of the ''PuTTYgen'' window) is ''EdDSA'' (short for //Edwards-curve DSA//), with the default ''255'' bits.\\ This will generate **//ed25519// keys** that are now recommended on the IPSL servers | ||
* {{:other:putty_23b.png?direct&500|}} | * {{:other:putty_23b.png?direct&500|}} | ||
- | * You could also use ''RSA'' and ''4096'' bits, but ''ed25519'' keys are now recommended on the IPSL servers | + | * You could also use ''RSA'' and ''4096'' bits, but ''ed25519'' keys are now recommended to access the [[https://documentations.ipsl.fr/spirit/spirit_clusters/head_nodes.html|IPSL servers]] |
* Click on the ''Generate'' button and move your mouse to generate some random information | * Click on the ''Generate'' button and move your mouse to generate some random information | ||
Line 174: | Line 174: | ||
* Click on the ''Save private key'' button, and create an ''id_ed25519**.ppk**'' file | * Click on the ''Save private key'' button, and create an ''id_ed25519**.ppk**'' file | ||
+ | * We recommend that you save this file in the the Windows [[other:ssh#configuration_files|ssh configuration directory]]\\ => ''C:\Users\your_windows_login\.ssh\id_ed25519.ppk'' | ||
* Note: files with a ''.ppk'' extension can only be used by ''PuTTY''/''pageant''. That's why you also need to //export// the private key, as shown below | * Note: files with a ''.ppk'' extension can only be used by ''PuTTY''/''pageant''. That's why you also need to //export// the private key, as shown below | ||