aboutsummaryrefslogtreecommitdiff
path: root/doc/design/assistant/sshpassword.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-07-23 18:46:09 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-07-23 18:46:09 -0400
commitbd9ef0f2530a848ff3f6a58a5e449b4e2b2209f8 (patch)
tree99f670e9265378da029377071db9c86d43a13faf /doc/design/assistant/sshpassword.mdwn
parentafa0d5c0d18f6f69ffbc55c26edde47b0c9ce949 (diff)
roadmap for next year's work
Diffstat (limited to 'doc/design/assistant/sshpassword.mdwn')
-rw-r--r--doc/design/assistant/sshpassword.mdwn12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/design/assistant/sshpassword.mdwn b/doc/design/assistant/sshpassword.mdwn
new file mode 100644
index 000000000..e38769867
--- /dev/null
+++ b/doc/design/assistant/sshpassword.mdwn
@@ -0,0 +1,12 @@
+Currently the assistant sets up dedicated ssh keys, that can just use
+git-annex. This is ok. The problem is that the initial 2 connections to the
+ssh server when setting up these keys involve a password prompt, which is
+done at the console unless the system happens to have a working ssh agent
+that can pop up a dialog. That can be confusing.
+
+It would be nice to have the webapp prompt for the password. Can it be done
+securely?
+
+This might come down to a simple change to the webapp to prompt for the
+password, and then rather a lot of pain to make the webapp use HTTPS so we
+can be pretty sure noone is sniffing the (localhost) connection.