7225c2bfc0
In order to record a semi-useful filename associated with the key, this required plumbing the filename all the way through to the remotes' storeKey and retrieveKeyFile. Note that there is potential for deadlock here, narrowly avoided. Suppose the repos are A and B. A sends file foo to B, and at the same time, B gets file foo from A. So, A locks its upload transfer info file, and then locks B's download transfer info file. At the same time, B is taking the two locks in the opposite order. This is only not a deadlock because the lock code does not wait, and aborts. So one of A or B's transfers will be aborted and the other transfer will continue. Whew! |
||
|---|---|---|
| .. | ||
| Backend.hs | ||
| BranchState.hs | ||
| Command.hs | ||
| Crypto.hs | ||
| Key.hs | ||
| KeySource.hs | ||
| Messages.hs | ||
| Option.hs | ||
| Remote.hs | ||
| TrustLevel.hs | ||
| UUID.hs | ||