From c654942c1ca3c7eec0644ed40238a9d53129ae93 Mon Sep 17 00:00:00 2001 From: tekkub Date: Sun, 6 Mar 2011 03:27:28 -0700 Subject: Trailing whitespace be damned --- _posts/2009-06-13-linux-set-up-git.markdown | 78 ++++++++++++++--------------- _posts/2009-06-13-mac-set-up-git.markdown | 68 ++++++++++++------------- _posts/2009-06-13-win-set-up-git.markdown | 62 +++++++++++------------ 3 files changed, 104 insertions(+), 104 deletions(-) diff --git a/_posts/2009-06-13-linux-set-up-git.markdown b/_posts/2009-06-13-linux-set-up-git.markdown index 1564fd9..8ed6731 100644 --- a/_posts/2009-06-13-linux-set-up-git.markdown +++ b/_posts/2009-06-13-linux-set-up-git.markdown @@ -16,21 +16,21 @@ _*If you don’t already know what Git is, Download and install the latest version of Git with Synaptic. We suggest you install git-core, git-gui, and git-doc. - + Open Synaptic Mark git-core, git-gui, and git-doc for installation git-core, git-gui, and git-doc are selected - + When you’ve selected git-core, git-gui, and git-doc, hit “Apply” to install them. - + Click Apply - + If you don’t have a package manager like Synaptic, or you’d rather install the necessary git components from the command line, you can alternatively run the script below: - + 
 		$ sudo apt-get install git-core git-gui git-docInstalls git-core, git-gui, and git-doc on your system
- + __*Note*__ Don’t worry that you don’t see an icon when it’s done. It’s not that kind of application. ##Next: Set Up SSH Keys @@ -45,30 +45,30 @@ To make sure you generate a brand new key, you need to check if one already exis

Need a quick lesson about Terminal?

Code blocks like those on this page are part of a scripting language called Bash. To use Bash scripts, we need to use an application that comes with Linux called Terminal.

- +

Input

 			$ echo 'This is input text'This tooltip tells you what's going on.
- +

A line that begins with the dollar sign ($) indicates a line of Bash script you need to type. To enter it, type the text that follows the $, hitting the return key at the end of each line. You can hover your mouse over each line for an explanation of what the script is doing.

- +

Output

 			This is output text.
- +

A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We’ve colored output text green in these bootcamp tutorials.

- +

User Specific Input

 			$ echo 'username'Outputs the text in the quotation marks.
- +

Areas of yellow text represent your own personal info, repos, etc. If it is part of an input ($) line, you should replace your it with your own info when you type it. If it is part of output text, it is just for your reference. It will automatically show your own info in Terminal.

- +

Good to know: There will be times when you type code, hit return, and all you are given is another prompt. Some actions that you execute in Terminal don’t have any output. Don’t worry, if there is ever a problem with your code, Terminal will let you know.

- +

Good to know: For security reasons, Terminal will not display what you type when entering passwords. Just type your password and hit the return key.

@@ -76,17 +76,17 @@ To make sure you generate a brand new key, you need to check if one already exis 1. Check for SSH keys. Have an existing kepair? You can skip to Step 4. First, we need to check for existing ssh keys on your computer: - + 
 	$ cd ~/.sshChecks to see if there is a directory named ".ssh" in your user directory
- + If it says “No such file or directory“ skip to __step 3__. Otherwise continue to __step 2__. 2. Backup and remove existing SSH keys. - + Since there is already an SSH directory you’ll want to back the old one up and remove it: - + 
 	$ lsLists all the subdirectories in the current directory
 	config  id_rsa  id_rsa.pub  known_hosts
@@ -98,37 +98,37 @@ To make sure you generate a brand new key, you need to check if one already exis
 3. 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.
-	
+
 	
 	$ ssh-keygen -t rsa -C "user_name@username.com"Creates a new ssh key using the provided email
 	Generating public/private rsa key pair.
 	Enter file in which to save the key (/home/your_user_directory/.ssh/id_rsa):
 	

-	
+
 	Now you need to enter a passphrase.
-	
+
 	

 		
Why do passphrases matter?

 		

 			
Passwords aren’t very secure, you already know this. If you use one that’s easy to remember, it’s easier to guess or brute-force (try many options until one works). If you use one that’s random it’s hard to remember, and thus you’re more inclined to write the password down. Both of these are Very Bad Things™. This is why you’re using ssh keys.

-			
+
 			
But using a key without a passphrase is basically the same as writing down that random password in a file on your computer. Anyone who gains access to your drive has gained access to every system you use that key with. This is also a Very Bad Thing™. The solution is obvious: add a passphrase.

-			
+
 			
But I don’t want to enter a long passphrase every time I use the key!

-			
+
 			
Neither do we! Thankfully, there’s a nifty little tool called ssh-agent that can save your passphrase securely so you don’t have to re-enter it. Most linux installations will automatically start ssh-agent for you when you log in.

-			
+
 			
For more information about SSH key passphrases, check out our help guide.

 		

 	

-	
+
 	
 	Enter passphrase (empty for no passphrase):
 	Enter same passphrase again:
 	

-	
+
 	Which should give you something like this:
-	
+
 	
 	Your identification has been saved in /home/your_user_directory/.ssh/id_rsa.
 	Your public key has been saved in /home/your_user_directory/.ssh/id_rsa.pub.
@@ -147,42 +147,42 @@ To make sure you generate a brand new key, you need to check if one already exis
 	|                 |
 	+-----------------+
 	

-	
+
 4. Add your SSH key to GitHub.
 
 	On the GitHub site _Click “Account Settings”_ > _Click “SSH Public Keys”_ > _Click “Add another public key”_
-	
+
 	__It’s important you copy your SSH key exactly as it is written without adding any newlines or whitespace.__ To ensure this, run the following code to copy the key to your clipboard.
-	
+
 	
 	$ sudo apt-get install xclipDownloads and installs xclip
 	$ xclip -sel clip < ~/.ssh/id_rsa.pubCopies the contents of the id_rsa.pub file to your clipboard
 	

-	
+
 	Now paste it into the “Key” field.
-	
+
 	Paste your SSH Key
-	
+
 	Hit “Add Key.”
 
 5. Test everything out.
 
 	To make sure everything is working you’ll now SSH to GitHub. Don’t change the “git@github.com” part. That’s supposed to be there.
-	
+
 	
 	$ ssh git@github.comAttempts to ssh to github
 	

-	
+
 	Which should give you this:
-	
+
 	
 	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. Type “yes”.
-	
+
 	
 	PTY allocation request failed on channel 0
 	Hi username! You've successfully authenticated, but GitHub does not provide shell access.
diff --git a/_posts/2009-06-13-mac-set-up-git.markdown b/_posts/2009-06-13-mac-set-up-git.markdown
index fa66b2d..95e4924 100644
--- a/_posts/2009-06-13-mac-set-up-git.markdown
+++ b/_posts/2009-06-13-mac-set-up-git.markdown
@@ -29,30 +29,30 @@ To make sure you generate a brand new key, you need to check if one already exis
 	
Need a quick lesson about Terminal?

 	

 		
Code blocks like those on this page are part of a scripting language called Bash. To use Bash scripts, we need to use an application that comes with your Mac called Terminal.

-		
+
 		
Input

 		
 			$ echo 'This is input text'This tooltip tells you what's going on.
 		

-		
+
 		
A line that begins with the dollar sign ($) indicates a line of Bash script you need to type. To enter it, type the text that follows the $, hitting the return key at the end of each line. You can hover your mouse over each line for an explanation of what the script is doing.

-		
+
 		
Output

 		
 			This is output text.
 		

-		
+
 		
A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We’ve colored output text green in these bootcamp tutorials.

-		
+
 		
User Specific Input

 		
 			$ echo 'username'Outputs the text in the quotation marks.
 		

-		
+
 		
Areas of yellow text represent your own personal info, repos, etc. If it is part of an input ($) line, you should replace it with your own info when you type it. If it is part of output text, it is just for your reference. It will automatically show your own info in Terminal.

-		
+
 		
Good to know: There will be times when you type code, hit return, and all you are given is another prompt. Some actions that you execute in Terminal don’t have any output. Don’t worry, if there is ever a problem with your code, Terminal will let you know.

-	
+
 		
Good to know: For security reasons, Terminal will not display what you type when entering passwords. Just type your password and hit the return key.

 	

 
@@ -60,17 +60,17 @@ To make sure you generate a brand new key, you need to check if one already exis
 1. Check for SSH keys. Have an existing kepair? You can skip to Step 4.
 
 	First, we need to check for existing ssh keys on your computer:
-	
+
 	
 	$ cd ~/.sshChecks to see if there is a directory named ".ssh" in your user directory
 	

-	
+
 	If it says “No such file or directory“ skip to __step 3__. Otherwise continue to __step 2__.
-	
+
 2. Backup and remove existing SSH keys.
-	
+
 	Since there is already an SSH directory you’ll want to back the old one up and remove it:
-	
+
 	
 	$ lsLists all the subdirectories in the current directory
 	config  id_rsa  id_rsa.pub  known_hosts
@@ -82,38 +82,38 @@ To make sure you generate a brand new key, you need to check if one already exis
 3. 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.
-	
+
 	
 	$ ssh-keygen -t rsa -C "your_email@youremail.com"Creates a new ssh key using the provided email
 	Generating public/private rsa key pair.
 	Enter file in which to save the key (/Users/your_user_directory/.ssh/id_rsa):
 	

-	
+
 	Now you need to enter a passphrase.
-	
+
 	

 		
Why do passphrases matter?

 		

 			
Passwords aren’t very secure, you already know this. If you use one that’s easy to remember, it’s easier to guess or brute-force (try many options until one works). If you use one that’s random it’s hard to remember, and thus you’re more inclined to write the password down. Both of these are Very Bad Things™. This is why you’re using ssh keys.

-			
+
 			
But using a key without a passphrase is basically the same as writing down that random password in a file on your computer. Anyone who gains access to your drive has gained access to every system you use that key with. This is also a Very Bad Thing™. The solution is obvious: add a passphrase.

-			
+
 			
But I don’t want to enter a long passphrase every time I use the key!

-			
+
 			
Neither do we! Thankfully, there’s a nifty little tool called ssh-agent that can save your passphrase securely so you don’t have to re-enter it. If you’re on OSX Leopard or later your keys can be saved in the system’s keychain to make your life even easier.

-			
+
 			
For more information about SSH key passphrases, check out our help guide.

 		

 	

 
-	
+
 	
 	Enter passphrase (empty for no passphrase):
 	Enter same passphrase again:
 	

-	
+
 	Which should give you something like this:
-	
+
 	
 	Your identification has been saved in /Users/your_user_directory/.ssh/id_rsa.
 	Your public key has been saved in /Users/your_user_directory/.ssh/id_rsa.pub.
@@ -132,41 +132,41 @@ To make sure you generate a brand new key, you need to check if one already exis
 	|                 |
 	+-----------------+
 	

-	
+
 4. Add your SSH key to GitHub.
 
 	On the GitHub site _Click “Account Settings”_ > _Click “SSH Public Keys”_ > _Click “Add another public key”_
-	
+
 	__It’s important you copy your SSH key exactly as it is written without adding any newlines or whitespace.__ To ensure this, run the following code to copy the key to your clipboard.
-	
+
 	
 	$ pbcopy < ~/.ssh/id_rsa.pubCopies the contents of the id_rsa.pub file to your clipboard
 	

-	
+
 	Now paste it into the “Key” field.
-	
+
 	Paste your SSH Key
-	
+
 	Hit “Add Key.”
 
 5. Test everything out.
 
 	To make sure everything is working you’ll now SSH to GitHub. Don’t change the “git@github.com” part. That’s supposed to be there.
-	
+
 	
 	$ ssh git@github.comAttempts to ssh to github
 	

-	
+
 	Which should give you this:
-	
+
 	
 	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. Type “yes”.
-	
+
 	
 	PTY allocation request failed on channel 0
 	Hi username! You've successfully authenticated, but GitHub does not provide shell access.
diff --git a/_posts/2009-06-13-win-set-up-git.markdown b/_posts/2009-06-13-win-set-up-git.markdown
index d3f2e4f..426b898 100644
--- a/_posts/2009-06-13-win-set-up-git.markdown
+++ b/_posts/2009-06-13-win-set-up-git.markdown
@@ -14,9 +14,9 @@ At the heart of GitHub is an open source version control system (VCS) called Git
 _*If you don’t already know what Git is, take a crash course._
 
 1. Download and install the latest version of msysgit.
-	
+
 	Use the default options for each step.
-	
+
 	Welcome page
 	Information
 	Select destination location
@@ -27,7 +27,7 @@ _*If you don’t already know what Git is, 
 	Installation complete
 
-	
+
 	__Do not use PuTTY if you are given the option. GitHub only provides support for openssh.__
 
 ##Next: Set Up SSH Keys
@@ -42,30 +42,30 @@ To make sure you generate a brand new key, you need to check if one already exis
 	
Need a quick lesson about Git Bash?

 	

 		
Code blocks like those on this page are part of a scripting language called Bash. To use Bash scripts, we need to use an application that was installed with Git called Git Bash.

-		
+
 		
Input

 		
 			$ echo 'This is input text'This tooltip tells you what's going on.
 		

-		
+
 		
A line that begins with the dollar sign ($) indicates a line of Bash script you need to type. To enter it, type the text that follows the $, hitting the return key at the end of each line. You can hover your mouse over each line for an explanation of what the script is doing.

-		
+
 		
Output

 		
 			This is output text.
 		

-		
+
 		
A line that does not begin with a $ is output text that is intended to give you information or tell you what to do next. We’ve colored output text green in these bootcamp tutorials.

-		
+
 		
User Specific Input

 		
 			$ echo 'username'Outputs the text in the quotation marks.
 		

-		
+
 		
Areas of yellow text represent your own personal info, repos, etc. If it is part of an input ($) line, you should replace it with your own info when you type it. If it is part of output text, it is just for your reference. It will automatically show your own info in Git Bash.

-		
+
 		
Good to know: There will be times when you type code, hit return, and all you are given is another prompt. Some actions that you execute in Git Bash don’t have any output. Don’t worry, if there is ever a problem with your code, Git Bash will let you know.

-	
+
 		
Good to know: For security reasons, Git Bash will not display what you type when entering passwords. Just type your password and hit the return key.

 	

 
@@ -73,17 +73,17 @@ To make sure you generate a brand new key, you need to check if one already exis
 1. Check for SSH keys. Have an existing kepair? You can skip to Step 4.
 
 	First, we need to check for existing ssh keys on your computer:
-	
+
 	
 	$ cd ~/.sshChecks to see if there is a directory named ".ssh" in your user directory
 	

-	
+
 	If it says “No such file or directory“ skip to __step 3__. Otherwise continue to __step 2__.
 
 2. Backup and remove existing SSH keys.
 
 	Since there is already an SSH directory you’ll want to back the old one up and remove it:
-	
+
 	
 	$ lsLists all the subdirectories in the current directory
 	config  id_rsa  id_rsa.pub  known_hosts
@@ -95,35 +95,35 @@ To make sure you generate a brand new key, you need to check if one already exis
 3. 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.
-	
+
 	
 	$ ssh-keygen -t rsa -C "user_name@username.com"Creates a new ssh key using the provided email
 	Generating public/private rsa key pair.
 	Enter file in which to save the key (/c/Users/your_user_directory/.ssh/id_rsa):
 	

-	
+
 	Now you need to enter a passphrase.
-	
+
 	

 		
Why do passphrases matter?

 		

 			
Passwords aren’t very secure, you already know this. If you use one that’s easy to remember, it’s easier to guess or brute-force (try many options until one works). If you use one that’s random it’s hard to remember, and thus you’re more inclined to write the password down. Both of these are Very Bad Things™. This is why you’re using ssh keys.

-			
+
 			
But using a key without a passphrase is basically the same as writing down that random password in a file on your computer. Anyone who gains access to your drive has gained access to every system you use that key with. This is also a Very Bad Thing™. The solution is obvious: add a passphrase.

-			
+
 			
But I don’t want to enter a long passphrase every time I use the key!

-			
+
 			
Neither do we! Thankfully, there’s a nifty little tool called ssh-agent that can save your passphrase securely so you don’t have to re-enter it. Unfortunately, it takes a little work to get it up and running on Windows. For more information check out our help guide.

 		

 	

-	
+
 	
 	Enter passphrase (empty for no passphrase):
 	Enter same passphrase again:
 	

-	
+
 	Which should give you something like this:
-	
+
 	
 	Your identification has been saved in /c/Users/your_user_directory/.ssh/id_rsa.
 	Your public key has been saved in /c/Users/your_user_directory/.ssh/id_rsa.pub.
@@ -134,31 +134,31 @@ To make sure you generate a brand new key, you need to check if one already exis
 4. Add your SSH key to GitHub.
 
 	On the GitHub site _Click “Account Settings”_ > _Click “SSH Public Keys”_ > _Click “Add another public key”_
-	
+
 	Open the id_rsa.pub file with a text editor (Notepad will do just fine). This is your SSH key. __It’s important you copy your SSH key exactly as it is written without adding any newlines or whitespace.__ Now paste it into the “Key” field.
-	
+
 	Paste your SSH Key
-	
+
 	Hit “Add Key.”
 
 5. Test everything out.
 
 	To make sure everything is working you’ll now SSH to GitHub. Don’t change the “git@github.com” part. That’s supposed to be there.
-	
+
 	
 	$ ssh git@github.comAttempts to ssh to github
 	

-	
+
 	Which should give you this:
-	
+
 	
 	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. Type “yes”.
-	
+
 	
 	PTY allocation request failed on channel 0
 	Hi username! You've successfully authenticated, but GitHub does not provide shell access.
-- 
cgit v1.3.1