Difference between revisions of "OpenBTS: Generating SSH Key untuk GitHub"

From OnnoWiki
Jump to navigation Jump to search
Line 65: Line 65:
 
* Klik "Add key"
 
* Klik "Add key"
  
==Step 4: Test everything out==
+
==Step 4: Test ==
  
To make sure everything is working, you'll now try SSHing to GitHub. When you do this, you will be asked to authenticate this action using your password, which was the passphrase you created earlier.
+
Coba SSH ke GitHub.
  
Open up your Terminal and type:
 
  
 
  ssh -T git@github.com
 
  ssh -T git@github.com
 
  # Attempts to ssh to github
 
  # Attempts to ssh to github
  
It's possible that you'll see this error message:
+
Jika gagal akan keluar message seperti,
  
 
  ...
 
  ...
Line 80: Line 79:
 
  debug1: No more authentication methods to try.
 
  debug1: No more authentication methods to try.
 
  Permission denied (publickey).
 
  Permission denied (publickey).
 
This is a known problem with certain Linux distributions. For a possible resolution, see our help article.
 
  
 
You may see this warning:
 
You may see this warning:
Line 99: Line 96:
  
 
If you're switching from HTTPS to SSH, you'll now need to update your remote repository URLs. For more information, see Changing a remote's URL.
 
If you're switching from HTTPS to SSH, you'll now need to update your remote repository URLs. For more information, see Changing a remote's URL.
 
 
 
 
 
 
 
  
 
==Referensi==
 
==Referensi==
  
 
* https://help.github.com/articles/generating-ssh-keys
 
* https://help.github.com/articles/generating-ssh-keys

Revision as of 09:16, 20 July 2014

Sumber: https://help.github.com/articles/generating-ssh-keys


Untuk berhubungan dengan github sangat di sarankan untuk menggunakan sambungan SSH. Langkah agar dapat melakukan hubungan tersebut adalah sebagai berikut.


Step 1: Cek SSH key

Cek SSH key di komputer yang kita gunakan

ls -al ~/.ssh
# Lists the files in your .ssh directory, if they exist

Cek dari daftar file yang ada, apakah ada file id_rsa.pub atau id_dsa.pub. Jika tidak ada file tersebut, lanjutkan ke step 2. Jika sudah ada, langsung ke step 3.

Step 2: Generate a new SSH key

Buat SSH key,

ssh-keygen -t rsa -C "your_email@example.com"
# Creates a new ssh key, using the provided email as a label
# Generating public/private rsa key pair.
# Enter file in which to save the key (/home/you/.ssh/id_rsa):

Selanjutnya masukan password


# Enter passphrase (empty for no passphrase): [Type a passphrase]
# Enter same passphrase again: [Type passphrase again]

Hasilnya kira-kira sebagai berikut

# Your identification has been saved in /home/you/.ssh/id_rsa.
# Your public key has been saved in /home/you/.ssh/id_rsa.pub.
# The key fingerprint is:
# 01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db your_email@example.com

Tambahkan key yang baru ke ssh-agent:

# start the ssh-agent in the background
eval "$(ssh-agent -s)"
# Agent pid 59566
ssh-add ~/.ssh/id_rsa

Step 3: Tambahkan SSH key ke GitHub

Untuk copy ke github

sudo apt-get install xclip
# Downloads and installs xclip. If you don't have `apt-get`, you might need to use another installer (like `yum`)
xclip -sel clip < ~/.ssh/id_rsa.pub
# Copies the contents of the id_rsa.pub file to your clipboard

Alternatively, using your favorite text editor, you can open the ~/.ssh/id_rsa.pub file and copy the contents of the file manually

Now that you have the key copied, it's time to add it into GitHub:

Step 4: Test

Coba SSH ke GitHub.


ssh -T git@github.com
# Attempts to ssh to github

Jika gagal akan keluar message seperti,

...
Agent admitted failure to sign using the key.
debug1: No more authentication methods to try.
Permission denied (publickey).

You may see this warning:

# The authenticity of host 'github.com (207.97.227.239)' can't be established.
# RSA key fingerprint is 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48.
# Are you sure you want to continue connecting (yes/no)?

Don't worry! This is supposed to happen. Verify that the fingerprint in your terminal matches the one we've provided up above, and then type "yes."

# Hi username! You've successfully authenticated, but GitHub does not
# provide shell access.

If that username is yours, you've successfully set up your SSH key! Don't worry about the "shell access" thing, you don't want that anyway.

If you receive a message about "access denied," you can read these instructions for diagnosing the issue.

If you're switching from HTTPS to SSH, you'll now need to update your remote repository URLs. For more information, see Changing a remote's URL.

Referensi