995e1e3c5d
recvkey was told it was receiving a HMAC key from a direct mode repo, and that confused it into rejecting the transfer, since it has no way to verify a key using that backend, since there is no HMAC backend. I considered making recvkey skip verification in the case of an unknown backend. However, that could lead to bad results; a key can legitimately be in the annex with a backend that the remote git-annex-shell doesn't know about. Better to keep it rejecting if it cannot verify. Instead, made the gcrypt special remote not set the direct mode flag when sending (and receiving) files. Also, added some recvkey messages when its checks fail, since otherwise all that is shown is a confusing error message from rsync when the remote git-annex-shell exits nonzero. |
||
|---|---|---|
| .. | ||
| AWS.hs | ||
| Chunked.hs | ||
| Encryptable.hs | ||
| Git.hs | ||
| Hooks.hs | ||
| Messages.hs | ||
| Special.hs | ||
| Ssh.hs | ||