git-annex/doc/devblog/day_164__back.mdwn
Joey Hess e213ef310f git-annex (5.20140717) unstable; urgency=high
* 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
2014-07-17 11:27:25 -04:00

17 lines
921 B
Markdown

My backlog is massive -- 181 items to answer. Will probably take the rest
of the month to get caught back up. Rather than digging into that yet,
spent today working on the webapp's ssh password prompting.
I simplified it so the password is entered on the same form as the rest
of the server's information. That made the UI easy to build, but
means that when a user already has a ssh key they want to use, they need
to select "existing ssh key"; the webapp no longer probes to automatically
detect that case.
Got the ssh password prompting in the webapp basically working, and it's a
*really* nice improvement! I even got it to work on Windows (eventually...).
It's still only in the `sshpassword` branch, since I need to test it more
and probably fix some bugs. In particular, when enabling a remote that
already exists, I think it never prompts for the password yet.
Today's work was sponsored by Nicola Chiapolini.