blog about departure from TC

[web/gag.com] / bdale / blog / posts / Strong_Keys.mdwn

diff --git a/bdale/blog/posts/Strong_Keys.mdwn b/bdale/blog/posts/Strong_Keys.mdwn
index a25838bd2d47086dea424f449c2f1925c52098b9..fc5bdc4a4cf5fffeaf5adc2dd5aa090268492afb 100644 (file)
--- a/bdale/blog/posts/Strong_Keys.mdwn
+++ b/bdale/blog/posts/Strong_Keys.mdwn
@@ -7,7 +7,8 @@ matters to me is that many Debian developers are in the process of
 transitioning to new, stronger gpg keys, and in the process also moving to 
 generate more strongly coded key signatures.
 
-While at Debconf9 this week, I succumbed to peer pressure, and have generated
+While at [Debconf9](http://debconf9.debconf.org/) this week, I succumbed 
+to peer pressure, and have generated
 a new 4096-bit RSA key 0xC095D941 which I will henceforth use as my primary 
 key.  I note in passing that my previous key 0xF2CF01A8 is just over 10 years
 old, and thanks largely to my intense business travel in recent years and
@@ -49,7 +50,7 @@ It bothered me that I had generated weak signatures with my new strong key,
 so I decided to re-sign the keys I had already signed with my new key so that
 all the signatures issued with my new strong key are strong signatures.  To
 do this, I used gpg's --edit-key option with gpg warped to point to 
-the caff home to 'delsig' the signatures I'd made to these keys, then use caff
+the caff home to 'delsig' the signatures I'd made to these keys, then used caff
 with the '--no-download' option to re-sign the keys and re-issue the associated
 emails.  Trolling ~/.caff/keys helped me discover which keys were in the 
 affected set, then I studied the command lines caff was feeding to gpg to