summaryrefslogtreecommitdiff
path: root/doc/devblog/day_133__db_and_bugfixes.mdwn
diff options
context:
space:
mode:
authorGravatar Richard Hartmann <richih@debian.org>2014-03-15 07:50:38 +0100
committerGravatar Richard Hartmann <richih@debian.org>2014-03-15 07:50:38 +0100
commit8f8ce35ec8f26999e01f70d6852b527c0410da4e (patch)
tree236d29eba7c998375912e06ce52e6f3d0096cc29 /doc/devblog/day_133__db_and_bugfixes.mdwn
parentd8f407cb1cc20eb1e6c2ea8de1e72743699651a2 (diff)
Typo & wording
Diffstat (limited to 'doc/devblog/day_133__db_and_bugfixes.mdwn')
-rw-r--r--doc/devblog/day_133__db_and_bugfixes.mdwn14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/devblog/day_133__db_and_bugfixes.mdwn b/doc/devblog/day_133__db_and_bugfixes.mdwn
index d8bb391ca..b844708dc 100644
--- a/doc/devblog/day_133__db_and_bugfixes.mdwn
+++ b/doc/devblog/day_133__db_and_bugfixes.mdwn
@@ -7,14 +7,14 @@ Not sure I'm ready to dive into that yet, so instead spent the rest of the
day working on small bugfixes and improvemnts. Only two significant ones..
Made the webapp use a constant time string comparison (from `securemem`)
-to check its auth token is valid. Could avoid a potential timing attack to
-guess the auth token, although that is theoretical. Just best practice to
-do this.
+to check if its auth token is valid. This could help avoid a potential
+timing attack to guess the auth token, although that is theoretical.
+Just best practice to do this.
Seems that openssh 6.5p1 had another hidden surprise (in addition to
its now-fixed bug in handing hostnames in `.ssh/config`) -- it broke
the method git-annex was using for stopping a cached ssh connection,
-which led to some timeouts for failing DNS lookups. If you see git-annex
-seeming to stall for a few seconds at startup/shutdown, that's maybe why
-(--debug will tell for sure). Seem to have found a workaround that avoids
-the problem.
+which led to some timeouts for failing DNS lookups. If git-annex seems
+to stall for a few seconds at startup/shutdown, that may be why
+(--debug will say for sure). I seem to have found a workaround that
+avoids this problem.