projects
/
web
/
gag.com
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
b96b217
)
typo
author
Bdale Garbee
<bdale@gag.com>
Tue, 28 Jul 2009 14:52:41 +0000
(16:52 +0200)
committer
Bdale Garbee
<bdale@gag.com>
Tue, 28 Jul 2009 14:52:41 +0000
(16:52 +0200)
bdale/blog/posts/Strong_Keys.mdwn
patch
|
blob
|
history
diff --git
a/bdale/blog/posts/Strong_Keys.mdwn
b/bdale/blog/posts/Strong_Keys.mdwn
index a25838bd2d47086dea424f449c2f1925c52098b9..beb5ff8d0b5f674443b4fe616ff149f020fd6312 100644
(file)
--- a/
bdale/blog/posts/Strong_Keys.mdwn
+++ b/
bdale/blog/posts/Strong_Keys.mdwn
@@
-49,7
+49,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
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 use
d
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
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