summaryrefslogtreecommitdiff
path: root/website/bugs/useful_information.mdwn
diff options
context:
space:
mode:
authormike castleman <m@mlcastle.net>2008-11-15 18:23:14 -0500
committermike castleman <m@mlcastle.net>2008-11-15 18:23:14 -0500
commita96625fb216143164f12191526939f4c0afcd5a9 (patch)
treebe95fde5875c7a8bc7297d7591824112743d2717 /website/bugs/useful_information.mdwn
parent91f3af2bbc51a1ff185365968790c8fdcab7097f (diff)
rename
Diffstat (limited to 'website/bugs/useful_information.mdwn')
-rw-r--r--website/bugs/useful_information.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/website/bugs/useful_information.mdwn b/website/bugs/useful_information.mdwn
new file mode 100644
index 0000000..0750354
--- /dev/null
+++ b/website/bugs/useful_information.mdwn
@@ -0,0 +1,10 @@
+I would like to know, at INFO (default) log level, when the
+monkeyspehere makes a "real" modification to my known_hosts file; that
+is, when it adds or deletes a key.
+
+Apparently this is hard because monkeysphere is currently configured to
+delete all keys and then add good keys, so a key added for the first
+time seems to the monkeysphere very similar to a key re-added ten
+seconds after last login.
+
+Still, from a UI perspective, I want to know what monkeysphere is doing.