trashSydowDev · December 15, 2015 03:32 · Dec 14, 2015 · Dec 14, 2015 · Dec 14, 2015 · Dec 14, 2015
diff --git a/README.md b/README.md
@@ -50,4 +50,5 @@ $ git config --global user.signingkey your-key
 ## Further Reading
 
 * [Email Self-defence](https://emailselfdefense.fsf.org)
-* [GNU Privacy Guard Howto](https://help.ubuntu.com/community/GnuPrivacyGuardHowto)
+* [GNU Privacy Guard Howto](https://help.ubuntu.com/community/GnuPrivacyGuardHowto)
+* [Beginners Guide to GnuPG](http://ubuntuforums.org/showthread.php?t=680292)
diff --git a/README.md b/README.md
@@ -13,7 +13,7 @@ Because after reading [this blog post](http://mikegerwitz.com/papers/git-horror-
 
 ## The solution
 
-Since Git `1.7.2`, one can sign commits using their own GPG key.
+Since Git `1.7.2`, one can sign commits (and tags) using their own GPG key.
 
 ### How
 

diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 ## Why
 
-Because after reading [this article](http://mikegerwitz.com/papers/git-horror-story.html) (sent by my dear friend @hugobessaa) I got paranoid. It's a little effort that can avoid a lot of trouble.
+Because after reading [this blog post](http://mikegerwitz.com/papers/git-horror-story.html) (sent by my dear friend @hugobessaa) I got paranoid. It's a little effort that can avoid a lot of trouble.
 
 ## The problem
 

diff --git a/README.md b/README.md
@@ -13,7 +13,7 @@ Because after reading [this article](http://mikegerwitz.com/papers/git-horror-st
 
 ## The solution
 
-Since Git `1.7.2`, one can sign commits usign their own GPG key.
+Since Git `1.7.2`, one can sign commits using their own GPG key.
 
 ### How
 

diff --git a/README.md b/README.md
@@ -13,7 +13,7 @@ Because after reading [this article](http://mikegerwitz.com/papers/git-horror-st
 
 ## The solution
 
-Since Git 1.7.2, one can sign commits usign their own GPG key.
+Since Git `1.7.2`, one can sign commits usign their own GPG key.
 
 ### How
 

diff --git a/README.md b/README.md
@@ -45,4 +45,9 @@ $ git config --global user.signingkey your-key
 [alias]
   commit = commit -S
 ```
-* Profit :moneybag:
+* Profit :moneybag:
+
+## Further Reading
+
+* [Email Self-defence](https://emailselfdefense.fsf.org)
+* [GNU Privacy Guard Howto](https://help.ubuntu.com/community/GnuPrivacyGuardHowto)
diff --git a/README.md b/README.md
@@ -25,7 +25,7 @@ $ brew install gpg
 ```sh
 $ gpg --gen-key # Default options are fine
 ```
-* Run gpg `--list-secret-keys` and copy the code after the first `/`. Something like this:
+* Now list all secret keys and copy the content from the `sec` row after the first `/`. Something like this:
 ```sh
 $ gpg --list-secret-keys
 /Users/your-user/.gnupg/secring.gpg

diff --git a/README.md b/README.md
@@ -21,7 +21,7 @@ Since Git 1.7.2, one can sign commits usign their own GPG key.
 ```sh
 $ brew install gpg
 ```
-* Generate a fresh gpg key:
+* Generate a fresh key:
 ```sh
 $ gpg --gen-key # Default options are fine
 ```

diff --git a/README.md b/README.md
@@ -17,15 +17,15 @@ Since Git 1.7.2, one can sign commits usign their own GPG key.
 
 ### How
 
-1. Install [`gpg`](https://www.gnupg.org). You can install it from Homebrew:
+* Install [`gpg`](https://www.gnupg.org). You can install it from Homebrew:
 ```sh
 $ brew install gpg
 ```
-2. Generate a fresh gpg key:
+* Generate a fresh gpg key:
 ```sh
 $ gpg --gen-key # Default options are fine
 ```
-3. Run gpg `--list-secret-keys` and copy the code after the first `/`. Something like this:
+* Run gpg `--list-secret-keys` and copy the code after the first `/`. Something like this:
 ```sh
 $ gpg --list-secret-keys
 /Users/your-user/.gnupg/secring.gpg
@@ -36,13 +36,13 @@ ssb   XXXXX/ZZZZZZZZ 2015-01-01
 
 # What you want is that YYYYYYYY
 ```
-4. Register your key to your Git configuration file:
+* Register your key to your Git configuration file:
 ```sh
 $ git config --global user.signingkey your-key
 ```
-5. You can now sign commits by using `git commit -S`. You might want to add it as an alias to your `.gitconfig`:
+* You can now sign commits by using `git commit -S`. You might want to add it as an alias to your `.gitconfig`:
 ```sh
 [alias]
   commit = commit -S
 ```
-6. Profit
+* Profit :moneybag:
diff --git a/README.md b/README.md
@@ -9,7 +9,7 @@ Because after reading [this article](http://mikegerwitz.com/papers/git-horror-st
 1. User changes the commit author using the `--author` option
 2. The commit then introduces a new bug (blaming the new author)
 3. Crackers explore this breach :skull:
-4. Audits will not be able to know who was the commit author
+4. An audit will not be able to identify who was the commit author
 
 ## The solution
 

diff --git a/README.md b/README.md
@@ -7,7 +7,7 @@ Because after reading [this article](http://mikegerwitz.com/papers/git-horror-st
 ## The problem
 
 1. User changes the commit author using the `--author` option
-2. The commit then introduces a new bug (blame on the new author)
+2. The commit then introduces a new bug (blaming the new author)
 3. Crackers explore this breach :skull:
 4. Audits will not be able to know who was the commit author
 

diff --git a/README.md b/README.md
@@ -0,0 +1,48 @@
+# Signing Git commits
+
+## Why
+
+Because after reading [this article](http://mikegerwitz.com/papers/git-horror-story.html) (sent by my dear friend @hugobessaa) I got paranoid. It's a little effort that can avoid a lot of trouble.
+
+## The problem
+
+1. User changes the commit author using the `--author` option
+2. The commit then introduces a new bug (blame on the new author)
+3. Crackers explore this breach :skull:
+4. Audits will not be able to know who was the commit author
+
+## The solution
+
+Since Git 1.7.2, one can sign commits usign their own GPG key.
+
+### How
+
+1. Install [`gpg`](https://www.gnupg.org). You can install it from Homebrew:
+```sh
+$ brew install gpg
+```
+2. Generate a fresh gpg key:
+```sh
+$ gpg --gen-key # Default options are fine
+```
+3. Run gpg `--list-secret-keys` and copy the code after the first `/`. Something like this:
+```sh
+$ gpg --list-secret-keys
+/Users/your-user/.gnupg/secring.gpg
+---------------------------------------
+sec   XXXXX/YYYYYYYY 2015-01-01
+uid                  Your Name (Your Comment) <[email protected]>
+ssb   XXXXX/ZZZZZZZZ 2015-01-01
+
+# What you want is that YYYYYYYY
+```
+4. Register your key to your Git configuration file:
+```sh
+$ git config --global user.signingkey your-key
+```
+5. You can now sign commits by using `git commit -S`. You might want to add it as an alias to your `.gitconfig`:
+```sh
+[alias]
+  commit = commit -S
+```
+6. Profit
No results found