From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Date: Mon, 4 Aug 2008 00:32:59 +0000 (-0400)
Subject: adding a new bug about the interaction between HostKeyAlias and monkeysphere-ssh... 
X-Git-Tag: monkeysphere_0.7-1~5
X-Git-Url: https://codewiz.org/gitweb?a=commitdiff_plain;ds=sidebyside;h=405fb7c3c93c4cef1f08a3edc9ea0d31c7a6df57;p=monkeysphere.git

adding a new bug about the interaction between HostKeyAlias and monkeysphere-ssh-proxycommand
---

diff --git a/website/bugs/hostkeyalias-confuses-monkeysphere.mdwn b/website/bugs/hostkeyalias-confuses-monkeysphere.mdwn
new file mode 100644
index 0000000..4f7df66
--- /dev/null
+++ b/website/bugs/hostkeyalias-confuses-monkeysphere.mdwn
@@ -0,0 +1,28 @@
+Consider the following snippet in `~/.ssh/config`:
+
+	 Host foo
+	 HostKeyAlias bar
+
+for a host which is *not* participating in the monkeysphere.
+
+For such a host, when using `monkeysphere-ssh-proxy-command`, the
+public keyservers will be queried on each attempted ssh connection
+(even after a successful connection).
+
+This appears to be because:
+
+* `ssh` itself will write a line to `~/.ssh/known_hosts`, but it will
+  be labeled with `bar` because of the `HostKeyAlias`. 
+
+* `monkeysphere` won't be able to find any mention of it in the
+  keyring (it's not in the monkeysphere)
+
+* `monkeysphere-ssh-proxycommand` won't be able to find it in the
+  `known_hosts` file because it looks for `foo`, which is never
+  matched.
+
+excessive keyserver querying is bad behavior, because it causes delays
+for the users, and puts excessive load on the public keyserver
+infrastructure.
+
+How can we resolve this?