OpenBTS: Generating SSH Key untuk GitHub - Revision history

Onnowpurbo: /* Step 4: Test */

2017-04-07T04:29:55Z

Step 4: Test

← Older revision		Revision as of 04:29, 7 April 2017
Line 78:		Line 78:

	Coba SSH ke GitHub.		Coba SSH ke GitHub.


	ssh -T git@github.com		ssh -T git@github.com

Onnowpurbo: /* Step 3: Tambahkan SSH key ke GitHub */

2017-04-07T04:29:39Z

Step 3: Tambahkan SSH key ke GitHub

← Older revision		Revision as of 04:29, 7 April 2017
Line 56:		Line 56:

	more ~/.ssh/id_rsa.pub		more ~/.ssh/id_rsa.pub

			Akan keluar kira2,

			ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDG3OY/Xz6gw4wV1X3vNlivDnXmW+v5RQ
			iPiXnWiir8IfZ7yqFNM9LWwGFUqbZEbIY2U22cGyZh+HE/OaEP5rggf5RRbedX4cP7iYJH
			is5VgOIN401dS/bhXGPRd4YZz/4y0stpnAOClsFP+rIMhaqortF2P onno@indo.net.id

	copy isinya ke clip & paste secara manual.		copy isinya ke clip & paste secara manual.

Onnowpurbo: /* Step 3: Tambahkan SSH key ke GitHub */

2014-07-24T05:43:50Z

Step 3: Tambahkan SSH key ke GitHub

← Older revision		Revision as of 05:43, 24 July 2014
Line 53:		Line 53:
	# Copies the contents of the id_rsa.pub file to your clipboard		# 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~~		Atau,

	~~Now that you have the key copied, it's time to add it into~~ GitHub:		more ~/.ssh/id_rsa.pub

			copy isinya ke clip & paste secara manual.

			Tambahkan ke GitHub:

	* Login ke http://github.com		* Login ke http://github.com

Onnowpurbo: /* Step 4: Test */

2014-07-20T02:18:21Z

Step 4: Test

← Older revision		Revision as of 02:18, 20 July 2014
Line 80:		Line 80:
	Permission denied (publickey).		Permission denied (publickey).

	~~You may see this~~ warning:		Jika benar, akan terlihat warning kira-kira seperti berikut:

	# The authenticity of host 'github.com (207.97.227.239)' can't be established.		# The authenticity of host 'github.com (207.97.227.239)' can't be established.
Line 86:		Line 86:
	# Are you sure you want to continue connecting (yes/no)?		# 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."~~		ketik 'yes'

	# Hi username! You've successfully authenticated, but GitHub does not		# Hi username! You've successfully authenticated, but GitHub does not
	# provide shell access.		# 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.~~		Jika username adalah username anda,maka SSH key berhasil.

	~~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==		==Referensi==

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

Onnowpurbo: /* Step 4: Test everything out */

2014-07-20T02:16:51Z

Step 4: Test everything out

← Older revision		Revision as of 02:16, 20 July 2014
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

Onnowpurbo: /* Step 3: Add your SSH key to GitHub */

2014-07-20T02:11:39Z

Step 3: Add your SSH key to GitHub

← Older revision		Revision as of 02:11, 20 July 2014
Line 43:		Line 43:
	ssh-add ~/.ssh/id_rsa		ssh-add ~/.ssh/id_rsa

	==Step 3: ~~Add your~~ SSH key to GitHub==		==Step 3: Tambahkan SSH key ke GitHub==

	Untuk copy ke github		Untuk copy ke github

Onnowpurbo at 06:45, 19 July 2014

2014-07-19T06:45:51Z

← Older revision		Revision as of 06:45, 19 July 2014
Line 2:		Line 2:


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

	We strongly recommend using an SSH connection when interacting with GitHub. SSH keys are a way to identify trusted computers, without involving passwords. The steps below will walk you through generating an SSH key and then adding the public key to your GitHub account.

	~~Tip~~: ~~We recommend that you regularly review your~~ SSH ~~keys list and revoke any that haven't been used in a while.~~		==Step 1: Cek SSH key==

	~~==Step 1: Check for~~ SSH ~~keys==~~		Cek SSH key di komputer yang kita gunakan

	~~First, we need to check for existing SSH keys on your computer. Open up your Terminal and type:~~

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

	~~Check the directory listing to see if you have files named either~~ id_rsa.pub or id_dsa.pub. ~~If you don't have either of those files~~, ~~go to~~ step 2. ~~Otherwise~~, ~~skip to~~ step 3.		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.

	~~Tip: If you have a new installation of Mac OSX, you will not have a ~/.ssh directory. It will be created when you run the ssh-keygen command in step 2 below~~.

	==Step 2: Generate a new SSH key==		==Step 2: Generate a new SSH key==

	~~To generate a new~~ SSH key, copy and paste the text below, making sure to substitute in your email address. The default settings are preferred, so when you're prompted to "Enter a file in which to save the key", just press Enter to continue.		Buat SSH key,

	ssh-keygen -t rsa -C "your_email@example.com"		ssh-keygen -t rsa -C "your_email@example.com"
Line 27:		Line 23:
	# Enter file in which to save the key (/home/you/.ssh/id_rsa):		# Enter file in which to save the key (/home/you/.ssh/id_rsa):

	~~Next, you'll be asked to enter a passphrase.~~		Selanjutnya masukan password

	~~Tip: We strongly recommend a very good, secure passphrase. For more information, see Working with SSH key passphrases.~~

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

	~~Which should give you something like this:~~		Hasilnya kira-kira sebagai berikut

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

	~~Then add your new~~ key ~~to the~~ ssh-agent:		Tambahkan key yang baru ke ssh-agent:

	# start the ssh-agent in the background		# start the ssh-agent in the background
Line 50:		Line 45:
	==Step 3: Add your SSH key to GitHub==		==Step 3: Add your SSH key to GitHub==

	~~Run the following code to~~ copy ~~the key to your clipboard.~~		Untuk copy ke github

	sudo apt-get install xclip		sudo apt-get install xclip

Onnowpurbo: /* Step 3: Add your SSH key to GitHub */

2014-07-19T06:11:04Z

Step 3: Add your SSH key to GitHub

← Older revision		Revision as of 06:11, 19 July 2014
Line 62:		Line 62:
	Now that you have the key copied, it's time to add it into GitHub:		Now that you have the key copied, it's time to add it into GitHub:

	~~Account settings buttonIn the user bar in the top-right corner of any page, click Account~~ settings.		* Login ke http://github.com
	~~SSH Keys menuClick SSH Keys in the left sidebar~~.		* Masuk ke https://github.com/settings/profile
	~~SSH Key buttonClick~~ Add SSH key.		* Masuk ke https://github.com/settings/ssh
	~~In the~~ Title ~~field, add a descriptive label for the new key. For example, if you're using a personal Mac, you might call this key "Personal MacBook Air".~~		* Klik "Add SSH key"
	~~The key fieldPaste your key into the "Key~~" ~~field.~~		* Tulis Title
	~~The~~ Add key ~~buttonClick Add key.~~		* Paste klip
	~~Confirm the action by entering your GitHub password.~~		* Klik "Add key"

	==Step 4: Test everything out==		==Step 4: Test everything out==

Onnowpurbo: New page: Sumber: https://help.github.com/articles/generating-ssh-keys We strongly recommend using an SSH connection when interacting with GitHub. SSH keys are a way to identify trusted computers...

2014-07-19T05:56:03Z

New page: Sumber: https://help.github.com/articles/generating-ssh-keys We strongly recommend using an SSH connection when interacting with GitHub. SSH keys are a way to identify trusted computers...

New page

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

We strongly recommend using an SSH connection when interacting with GitHub. SSH keys are a way to identify trusted computers, without involving passwords. The steps below will walk you through generating an SSH key and then adding the public key to your GitHub account.

Tip: We recommend that you regularly review your SSH keys list and revoke any that haven't been used in a while.

==Step 1: Check for SSH keys==

First, we need to check for existing SSH keys on your computer. Open up your Terminal and type:

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

Check the directory listing to see if you have files named either id_rsa.pub or id_dsa.pub. If you don't have either of those files, go to step 2. Otherwise, skip to step 3.

Tip: If you have a new installation of Mac OSX, you will not have a ~/.ssh directory. It will be created when you run the ssh-keygen command in step 2 below.

==Step 2: Generate a new SSH key==

To generate a new SSH key, copy and paste the text below, making sure to substitute in your email address. The default settings are preferred, so when you're prompted to "Enter a file in which to save the key", just press Enter to continue.

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):

Next, you'll be asked to enter a passphrase.

Tip: We strongly recommend a very good, secure passphrase. For more information, see Working with SSH key passphrases.

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

Which should give you something like this:

# 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

Then add your new key to the ssh-agent:

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

==Step 3: Add your SSH key to GitHub==

Run the following code to copy the key to your clipboard.

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:

Account settings buttonIn the user bar in the top-right corner of any page, click Account settings.
SSH Keys menuClick SSH Keys in the left sidebar.
SSH Key buttonClick Add SSH key.
In the Title field, add a descriptive label for the new key. For example, if you're using a personal Mac, you might call this key "Personal MacBook Air".
The key fieldPaste your key into the "Key" field.
The Add key buttonClick Add key.
Confirm the action by entering your GitHub password.

==Step 4: Test everything out==

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.

Open up your Terminal and type:

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

It's possible that you'll see this error message:

...
Agent admitted failure to sign using the key.
debug1: No more authentication methods to try.
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:

# 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==

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