summaryrefslogtreecommitdiff
path: root/website/bugs
diff options
context:
space:
mode:
authorJameson Graef Rollins <jrollins@phys.columbia.edu>2008-08-18 08:48:16 -0700
committerJameson Graef Rollins <jrollins@phys.columbia.edu>2008-08-18 08:48:16 -0700
commit59d3a09628ae2cbf90cd34265edb438728b40ea3 (patch)
treeeadf0d982a6b2a4be04d7ae8b5db0e6fd42ca73e /website/bugs
parentd7d179a481d549a600e44d24d19df219ed497cfd (diff)
rewording but report.
Diffstat (limited to 'website/bugs')
-rw-r--r--website/bugs/revoke-hostname-revoking-wrong-userid.mdwn26
1 files changed, 13 insertions, 13 deletions
diff --git a/website/bugs/revoke-hostname-revoking-wrong-userid.mdwn b/website/bugs/revoke-hostname-revoking-wrong-userid.mdwn
index 847b613..f785a9d 100644
--- a/website/bugs/revoke-hostname-revoking-wrong-userid.mdwn
+++ b/website/bugs/revoke-hostname-revoking-wrong-userid.mdwn
@@ -76,19 +76,19 @@ seems to be doing it pretty consistently for me at the moment:
Run 'monkeysphere-server publish-key' to publish the revocation.
servo:~ 0$
-Clearly this is unacceptable. Because of more inadequacies in gpg,
-you can't specify a uid to revoke from the command line. The uid
-revokation requires an edit-key script, which we have used before, but
-you have to specify by "number" which uid to revoke. We currently try
-to guess the number from the ordering of the output of list-key. This
-however is not always accurate. I don't have a good solution for a
-fix at the moment. Suggestions are most welcome. It may just require
-some trial and error with edit-key to come up with something workable.
+Clearly this is unacceptable. gpg does not let you can't specify a
+uid to revoke from the command line. The uid revokation can only be
+done through edit-key. We do edit-key scripting in other contexts,
+but to revoke a user id you have to specify the uid by "number". We
+currently try to guess the number from the ordering of the output of
+list-key. However, this output does not appear to coincide with the
+ordering in edit-key. I don't have a good solution or fix at the
+moment. Suggestions are most welcome. It may just require some trial
+and error with edit-key to come up with something workable.
-This underlines the problem that gpg sucks ass as a tool for
-manipulating gpg keyrings non-interactively. This is a big problem.
-We need something better that we can use. I would gladly rewrite
-everything if there was a better tool out there, but I don't know of
-one.
+This underlines the problem that gpg is currently not very well suited
+for manipulating gpg keyrings non-interactively. It's possible that I
+just haven't figured out how to do it yet, but it's not very clear if
+it is possible. It would be nice to have some alternate tools to use.
-- Big Jimmy.