These instructions are for users who are using Linux®, and do not have a key.

If you use an SFTP client other than OpenSSH in Linux or WinSCP on Windows™, contact your company's IT support team for help generating and uploading SSH keys.

1. Generate a key.
   1. Enter: ssh-keygen -t rsa

      The type of 'rsa' means RSA protocol 2 ('rsa1' means RSA protocol 1). You see a prompt similar to:

      
      Generating public/private rsa key pair.                                                           
      

   2. Enter a name for the file where the key will be saved (/home/myself/.ssh/id_rsa).
   3. Click Enter.

      If you put a passphrase on your private key, you need to enter that passphrase every time you connect via SFTP. If you want fully unattended SFTP, use no passphrase and click Enter when prompted for a passphrase.

      Sample output:

      
      Enter passphrase (empty for no passphrase): *[something]*
      Enter same passphrase again: *[something]*
      Your identification has been saved in /home/myself/.ssh/id_rsa.
      Your public key has been saved in /home/myself/.ssh/id_rsa.pub.
      The key fingerprint is: 3f:5c:79:05:64:0e:2f:bb:ab:35:db:a4:08:71:84:9f myself@myself-L2
      The key's randomart image is:
      
      +--[ RSA 2048]----+
      |            ..+  |
      |         .   = . |
      |        . . . o .|
      |         o . + . |
      |        S E + .  |
      |         = . o   |
      |        . + + .  |
      |         . + B   |
      |          o.+ .  |
      +-----------------+
      

2. Enter the following to review the resulting public key.

   myself@myself-L2:~$ cat /home/myself/.ssh/id_rsa.pub

   On Windows use type instead of cat.

   If your results look like the following example, you must convert it to RFC4716 format for use by proftpd.

   
   ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEArHx7BJxf/IBVNSdyg2BLdI21j5+6vUBprhLsNz9MFHeZCZG9PpOdYKnpM5conCZHtLoAkGOsW5jW/67Eq0HtkdqMLVyRZTehaAuqGjpPbVQGCqtAnqLBqN7MnUh+QeaV4Ov+UXhsrOoMSGa6tE83JLvU5JTXr/tqr+V6K47oiGfKwVOo5UC2Quxy8IP3rFBdhDHnh+y1WY3hnwocrCQqmzndHkc0/YpdHL/jO/UN7IlyGCqUSU2KUIT117tsTgMZJZxUkh6oF/aEPwkeXUS8cYTDFdNAv075c9bwbvvz0efLBr/EXUtlmAUvsYi+gfASw7S44ylZu/LErWRBwRGSBw== myself@myself-L2
   

   If your public key looks like the following example, you do not need to convert.

   
   ---- BEGIN SSH2 PUBLIC KEY ----
   Comment: "dsa-key-20091012"
   AAAAB3Nza...
   ---- END SSH2 PUBLIC KEY ----
   

   Do not provide fingerprint values such as "3f:5c:79:05:64:0e:2f:bb:ab:35:db:a4:08:71:84:9f".

3. If necessary to convert to RFC4716, run myself@myself-L2:~$ ssh-keygen -e -f ~/.ssh/id_rsa.pub > /tmp/authorized_keys.
4. Upload your key to Acoustic Campaign.

   Transfer your file to your SFTP account. In the example below, substitute your Acoustic Campaign Pod number for the X. Find your login and SFTP server here. Substitute your SFTP login name for user@example.com.

   myself@myself-L2:~$ scp /tmp/authorized_keys "user@example.com"@transfer-campaign-us-X.goacoustic.com:/.ssh/authorized_keys

   Next, test login over SFTP and see if it prompts you for a password. If you are not prompted for a password, the change has been successful.