Differences
This shows you the differences between two versions of the page.
aerocom:user-server [2013-11-01 13:37:51] jang added some more links |
aerocom:user-server [2022-05-31 09:29:31] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== How to get access to the aerocom user server ===== | ||
- | 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:// | ||
- | a terminal program and [[http:// | ||
- | ==== Access ==== | ||
- | |||
- | 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) | ||
- | * An account is opened upon sending a request for an account to michael.schulz@met.no and jan.griesfeller@met.no | ||
- | * The project description is made available to AeroCom participants via this [[aerocom: | ||
- | * Results from analysis are reported to AeroCom workshops | ||
- | * Publication-Coauthorship is offered to model and data author. See [[aerocom: | ||
- | |||
- | 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. | ||
- | 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. | ||
- | |||
- | ==== How to create a ssh key ==== | ||
- | |||
- | === Step 1: Check for SSH keys === | ||
- | First, we need to check for existing ssh keys on your computer. Open up Terminal and run: | ||
- | < | ||
- | $ ls | ||
- | # Lists the files in your .ssh directory</ | ||
- | |||
- | Check the directory listing to see if you have a file named either < | ||
- | If you don't have either of those files go | ||
- | to step 2. Otherwise, you already have an existing keypair, and you can skip to step 3. | ||
- | |||
- | === Step 2: Generate a new SSH key === | ||
- | |||
- | 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. | ||
- | < | ||
- | Generating public/ | ||
- | ... | ||
- | </ | ||
- | |||
- | |||
- | Enter the path to the file that will hold the key: By default, the file name $HOME/ | ||
- | appears in parentheses. | ||
- | |||
- | < | ||
- | |||
- | 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. | ||
- | |||
- | < | ||
- | |||
- | Re-enter the passphrase to confirm it: Type your passphrase once again to confirm it. | ||
- | |||
- | < | ||
- | Enter same passphrase again: <Type the passphrase> | ||
- | Your identification has been saved in / | ||
- | Your public key has been saved in / | ||
- | The key fingerprint is: | ||
- | 0b: | ||
- | </ | ||
- | |||
- | === Step 3: Send your public key to jan.griesfeller@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</ | ||
- | |||
- | ==== Further information ==== | ||
- | This page was partly stolen from [[http:// | ||
- | [[https:// | ||
- | If you want to know how key authentication works, please read [[http:// | ||
- | this article about public key cryptography]]. |