summaryrefslogtreecommitdiff
path: root/website/bugs/useful-information.mdwn
diff options
context:
space:
mode:
authorMatt Goins <mjgoins@openflows.com>2008-11-16 11:18:38 -0500
committerMatt Goins <mjgoins@openflows.com>2008-11-16 11:18:38 -0500
commite7c994d6f67d380ed0de21f1500ec395eaab6640 (patch)
treee4c81a45e2dcfdd46409beab222d122751f5f6d7 /website/bugs/useful-information.mdwn
parent9aec501a27b51523165a05c4c4da0cc9251424e8 (diff)
parent5d9949335aeb1dec04f530cbb3dfcac24288706a (diff)
Merge commit 'dkg/master'
Diffstat (limited to 'website/bugs/useful-information.mdwn')
-rw-r--r--website/bugs/useful-information.mdwn24
1 files changed, 24 insertions, 0 deletions
diff --git a/website/bugs/useful-information.mdwn b/website/bugs/useful-information.mdwn
new file mode 100644
index 0000000..62094bb
--- /dev/null
+++ b/website/bugs/useful-information.mdwn
@@ -0,0 +1,24 @@
+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.
+
+------
+
+It looks like jrollins committed a change for reporting at INFO level
+when a host key gets added by the monkeysphere:
+2459fa3ea277d7b9289945748619eab1e3441e5c
+
+When i connect to a host whose key is not already present in my
+known_hosts file, i get the following to stderr:
+
+ ms: * new key for squeak.fifthhorseman.net added to known_hosts file.
+
+This doesn't fully close this bug, because we aren't notifying on key
+deletion, afaict.