e213ef310f
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
Markdown
Did some more exploration and perf tuning and thinking on caching
|
|
databases, and am pretty sure I know how I want to implement it. Will be
|
|
several stages, starting with using it for generating views, and ending(?)
|
|
with using it for direct mode file mappings.
|
|
|
|
Not sure I'm ready to dive into that yet, so instead spent the rest of the
|
|
day working on small bugfixes and improvements. Only two significant ones..
|
|
|
|
Made the webapp use a constant time string comparison (from `securemem`)
|
|
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 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.
|