Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
aerocom:user-server [2013-11-01 13:10:01]
jang
aerocom:user-server [2021-04-16 07:51:35]
annac
Line 1: Line 1:
-===== How to get access to the aerocom user server =====+===== How to get access to the aerocom user server (Unix and MacOSX)===== 
 +This guide assumes that you are working with an Unix based (including OS X) operating system.\\ 
 +If you are using windows, you might want to have a look at [[http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html|putty]] 
 + a terminal program and [[http://winscp.net/eng/index.php|WinSCP]] a secure copy client.
  
 ==== Access ==== ==== Access ====
Line 5: Line 8:
 Conditions for access to the AeroCom data server:  Conditions for access to the AeroCom data server: 
   * A short project description of the planned analysis is send to AeroCom contact (michael.schulz@met.no)   * A short project description of the planned analysis is send to AeroCom contact (michael.schulz@met.no)
-  * An account is opened upon sending a request for an account to michael.schulz@met.no and jan.griesfeller@met.no+  * An account is opened upon sending a request for an account to (Michael) michael.schulz@met.no and (Anna) annac@met.no and (Jan) jan.griesfeller@met.no
   * The project description is made available to AeroCom participants via this [[aerocom:data_base_user_overview|wiki page]]   * The project description is made available to AeroCom participants via this [[aerocom:data_base_user_overview|wiki page]]
   * Results from analysis are reported to AeroCom workshops   * Results from analysis are reported to AeroCom workshops
   * Publication-Coauthorship is offered to model and data author. See [[aerocom:data_policy|data policy]]   * Publication-Coauthorship is offered to model and data author. See [[aerocom:data_policy|data policy]]
  
-At first you will get a username and a password for ftp.aerocom.met.no only. The main purpose for it is to send us data. +At first you will get a username and a password for this wikiTo get access to the user server __aerocom-users.met.no__, you have to send us a ssh public key since password authentication is disabled for security reasons on the user server. You can connect to the user server via //**ssh**//, but also use //**scp**// and //**rsync**// for data transfers. 
-In order to get access to the user server aerocom-users.met.no as well, you have to send us a ssh public key since password authentication is disabled for security reasons on the user server.+For more details on AeroCom database, please read about [[https://wiki.met.no/aerocom/data_submission|data submission procedure]].
  
 ==== How to create a ssh key ==== ==== How to create a ssh key ====
Line 21: Line 24:
 # Lists the files in your .ssh directory</code> # Lists the files in your .ssh directory</code>
  
-Check the directory listing to see if you have a file named either <key>id_rsa.pub </key> or <key>id_dsa.pub</key>.  +Check the directory listing to see if you have a file named <key>id_rsa.pub </key>.  
-If you don'have either of those files go  +If you don'tgo to step 2. If you already have an existing keypair, skip to step 3.
-to step 2. Otherwise, you already have an existing keypair, and you can skip to step 3.+
  
 === Step 2: Generate a new SSH key === === Step 2: Generate a new SSH key ===
-=== Step 3: Send your key to jan.griesfeller@met.no ===+ 
 +To generate a new SSH key, enter the code below. We want the default settings so when asked to enter a file in which to save the key,  
 +just press enter. 
 +<code> $ ssh-keygen -t rsa -C "my comment" 
 +Generating public/private rsa key pair. 
 +... 
 +</code> 
 + 
 + 
 +Enter the path to the file that will hold the key: By default, the file name $HOME/.ssh/id_rsa, which represents an RSA v2 key,  
 +appears in parentheses. 
 + 
 +<code> Enter file in which to save the key (/home/user/.ssh/id_rsa): <return> </code> 
 + 
 +Enter a passphrase for using your key: The passphrase you enter will be used for encrypting your private key. A good passphrase should be alphanumeric having 10-30 character length. You can also use a null passphrase however this can cause a security loophole. 
 + 
 +<code>Enter passphrase (empty for no passphrase): <Type the passphrase> </code> 
 + 
 +Re-enter the passphrase to confirm it: Type your passphrase once again to confirm it. 
 + 
 +<code> 
 +Enter same passphrase again: <Type the passphrase> 
 +Your identification has been saved in /home/user/.ssh/id_rsa. 
 +Your public key has been saved in /home/user/.ssh/id_rsa.pub. 
 +The key fingerprint is: 
 +0b:fa:3c:b8:73:71:bf:58:57:eb:2a:2b:8c:2f:4e:37 user@myLocalHost 
 +</code> 
 + 
 +=== Step 3: Send your public key to jan.griesfeller@met.no and anna.benedictow@met.no === 
 + 
 +In the folder ~/.ssh you will find file(s) ending with .pub. Please send us the one you just created e.g. <key> id_rsa.pub</key>. **And no other file** 
 + 
 +==== Further information ==== 
 +This page was partly stolen from [[http://en.wikipedia.org/wiki/Ssh-keygen|wikipedia]] and  
 +[[https://help.github.com/articles/generating-ssh-keys|github]].\\ 
 +If you want to know how key authentication works, please read [[http://en.wikipedia.org/wiki/Public-key_cryptography| 
 +this article about public key cryptography]].
  • aerocom/user-server.txt
  • Last modified: 2022-05-31 09:29:31
  • (external edit)