From b4af48a66968f1e9c7d927e62d0de4a6e9d0bf31 Mon Sep 17 00:00:00 2001 From: "http://johan.kiviniemi.name/" Date: Thu, 1 May 2014 20:46:19 +0000 Subject: [PATCH] Added a comment --- .../comment_3_87c980feb28a05d12a259fb2b3091cdf._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_3_87c980feb28a05d12a259fb2b3091cdf._comment diff --git a/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_3_87c980feb28a05d12a259fb2b3091cdf._comment b/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_3_87c980feb28a05d12a259fb2b3091cdf._comment new file mode 100644 index 0000000000..deface16f2 --- /dev/null +++ b/doc/bugs/ssh-askpass_locks_me_out_of_x_console/comment_3_87c980feb28a05d12a259fb2b3091cdf._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://johan.kiviniemi.name/" + nickname="Johan" + subject="comment 3" + date="2014-05-01T20:46:18Z" + content=""" ++1 for always setting up a key. I have had to temporarily disable a key and set up an account password or replicate what git-annex does (generate key, add pseudo host to .ssh/config, add remote, add entry to remote:.ssh/authorized_keys) manually when adding remotes a number of times. +"""]]