summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2017-05-11 18:06:24 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2017-05-11 18:06:24 -0400
commit8dad413ea98a6558a0ad48ef626d914595c30d22 (patch)
tree65a6b4a1197fb4c9e19f89cefe9332b9488ea282
parenta087841ae775a14197c1550488f54b5761f4700b (diff)
devblog
-rw-r--r--doc/devblog/day_457__improved_ssh_password_prompting.mdwn20
-rw-r--r--get_-J_cannot_be_used_with_password-based_authentication/comment_1_5da63cf5fa93120c85b98077fba51488._comment19
2 files changed, 39 insertions, 0 deletions
diff --git a/doc/devblog/day_457__improved_ssh_password_prompting.mdwn b/doc/devblog/day_457__improved_ssh_password_prompting.mdwn
new file mode 100644
index 000000000..0b99cbce6
--- /dev/null
+++ b/doc/devblog/day_457__improved_ssh_password_prompting.mdwn
@@ -0,0 +1,20 @@
+After a month away building [debug-me](https://debug-me.branchable.com/)
+I'm back working on git-annex. I hope debug-me will be useful for debugging
+git-annex in some situations BTW.
+
+Pushed a release yesterday that was mostly changes from back in March.
+It also updated the git bundled with git-annex to fix the recent git-shell
+security hole.
+
+After work on Monday and today, I am caught up with all the recent month's
+backlog, but still have 230 old backlogged messages to get to.
+
+The first consequental thing I got back to was improving ssh password
+prompting when git-annex is running concurrently with -J. It used to start
+up several ssh's at the same time, so connection caching didn't kick in,
+and there could be a bunch of ssh password prompts at the same time. Now
+there will never be more than one ssh password prompt at once, and only one
+prompt per host. (As long as connection caching is enabled.)
+
+That mostly works, but `git annex drop -J` exposes a bug in it, which I'll
+have to get back to tomorrow.
diff --git a/get_-J_cannot_be_used_with_password-based_authentication/comment_1_5da63cf5fa93120c85b98077fba51488._comment b/get_-J_cannot_be_used_with_password-based_authentication/comment_1_5da63cf5fa93120c85b98077fba51488._comment
new file mode 100644
index 000000000..4e0c93fb1
--- /dev/null
+++ b/get_-J_cannot_be_used_with_password-based_authentication/comment_1_5da63cf5fa93120c85b98077fba51488._comment
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-05-11T21:57:24Z"
+ content="""
+Current status: It's implemented, but not for `GIT_SSH` yet.
+
+`git annex get -J 3` seems to work well.
+
+`git annex drop -J 3` sometimes (once per 5 or so tries) runs
+2 ssh processes both prompting at once. For example:
+
+ 21555 pts/3 S+ 0:00 | \_ ssh localhost -S .git/annex/ssh/localhost -o ControlMaster=auto -o ControlPersist=yes -T git-annex-shell 'lockcontent' '/~/tmp/b/a' 'SHA256E-s30--ec748fe42378798b82ddf4e6b3e778a0cbc5d76d458685af01dc1f09cc423eb7' --uuid ad19d177-519e-4440-a9c9-0c9cddd99db2
+ 21556 pts/3 S+ 0:00 | \_ ssh localhost -S .git/annex/ssh/localhost -o ControlMaster=auto -o ControlPersist=yes -n -T git-annex-shell inannex .
+
+The inannex is what's used to bring up the ssh connection, so
+I don't immediately understand how the lockcontent could run before
+the ssh connection is brought up.
+"""]]