summaryrefslogtreecommitdiff
path: root/website
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>2008-08-06 14:49:55 -0400
committerDaniel Kahn Gillmor <dkg@fifthhorseman.net>2008-08-06 14:49:55 -0400
commit55e7ac39ba0e3e200d23302b6ac0efcfaa967a05 (patch)
tree305038851092a6ffd6f18ded614df17e0da67b7f /website
parent65bb1dc18f691f341895c44f1078379f8bfee321 (diff)
suggesting user-friendliness improvements for monkeysphere gen-key
Diffstat (limited to 'website')
-rw-r--r--website/bugs/monkeysphere-gen-key-should-guess-KeyID.mdwn23
1 files changed, 23 insertions, 0 deletions
diff --git a/website/bugs/monkeysphere-gen-key-should-guess-KeyID.mdwn b/website/bugs/monkeysphere-gen-key-should-guess-KeyID.mdwn
new file mode 100644
index 0000000..f50cbf0
--- /dev/null
+++ b/website/bugs/monkeysphere-gen-key-should-guess-KeyID.mdwn
@@ -0,0 +1,23 @@
+[[meta title="`monkeysphere gen-key` should guess at KeyID if none provided"]]
+
+Currently, if you have a single private key in your GnuPG keyring, and
+you call:
+
+ monkeysphere gen-key
+
+(with no additional arguments), it will report an error.
+
+It would be more user-friendly if we could guess which key to use. I
+suggest:
+
+* If the user only has no GPG secret keys at all, it should fail, and
+ suggest that the user create a key first, then re-run `monkeysphere
+ gen-key`. (`monkeysphere` could actually invoke `gpg --gen-key` for
+ the user directly, if the user wants that)
+
+* If the user only has one GPG secret key, it should use that key.
+
+* If the user has more than one GPG secret key, `monkeysphere` should
+ fail, and report the different key IDs that they user might want to
+ select (reporting which keys already have authorization subkeys or
+ the authorization capability on the primary key would be useful too)