File: day_308__ssh-agent.mdwn

package info (click to toggle)
git-annex 10.20230126-3
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 69,344 kB
  • sloc: haskell: 74,654; javascript: 9,103; sh: 1,304; makefile: 203; perl: 136; ansic: 44
file content (16 lines) | stat: -rw-r--r-- 888 bytes parent folder | download | duplicates (11)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Turns out ssh-agent is the cause of the unknown UUID bug! I got a tip
about this from a user, and was quickly able to reproduce the bug that had
eluded me so long. Anyone who has run `ssh-add` and is using ssh-agent
would see the bug.

It was easy enough to fix as it turns out. Just need to set IdentitiesOnly
in .ssh/config where git-annex has set up its own IdentityFile to ensure
that its special purpose ssh key is used rather than whatever key the
ssh-agent has loaded into it. I do wonder why ssh behaves this way -- why
would I set an IdentityFile for a host if I didn't want ssh to use it?

Spent the rest of the day cleaning up after the bug. Since this affects so
many people, I automated the clean up process. The webapp will
detect repositories with this problem, and the user just has to click to
clean up. It'll then correct their .ssh/config and re-enable the
repository.