From 907cf0c6687f28fd8d9daefd930ef81f581d6e82 Mon Sep 17 00:00:00 2001
From: "http://joeyh.name/" <joey@web>
Date: Sun, 14 Apr 2013 18:34:45 +0000
Subject: [PATCH] Added a comment: ssh agent?

---
 ..._10282c4352075c8d148b8674973b7b16._comment | 22 +++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_14_10282c4352075c8d148b8674973b7b16._comment

diff --git a/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_14_10282c4352075c8d148b8674973b7b16._comment b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_14_10282c4352075c8d148b8674973b7b16._comment
new file mode 100644
index 0000000000..0b1da90293
--- /dev/null
+++ b/doc/bugs/The_restricted_ssh_key_pair_makes_password_login___40__nearly__41___impossible/comment_14_10282c4352075c8d148b8674973b7b16._comment
@@ -0,0 +1,22 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ nickname="joey"
+ subject="ssh agent?"
+ date="2013-04-14T18:34:45Z"
+ content="""
+The only other thing I can think of is that if you have a ssh-agent, it might somehow be caching the git-annex key and incorrectly sending it to ssh. If this were the case, then unsetting `SSH_AUTH_SOCK` or stopping the agent would presumably make the problem go away.
+
+In @marvin's log, I see:
+
+<pre>
+debug1: Offering RSA public key: marvin@marvin-U-100
+</pre>
+
+This is different from what I see when ssh is using a regular key in `.ssh/`:
+
+<pre>
+debug1: Offering RSA public key: /home/joey/.ssh/id_rsa
+</pre>
+
+Marvin's log does not show where it gets this \"marvin@marvin-U-100\".. which makes me suspect it comes from a ssh agent.
+"""]]