However, this is not working for gcrypt repos with a mangled hostname. Problem is that the locked down key is installed before the repo is initialized, so git-annex-shell refuses to allow the gcrypt special remote to do its setup. |
||
|---|---|---|
| .. | ||
| AWS.hs | ||
| Delete.hs | ||
| Edit.hs | ||
| IA.hs | ||
| Local.hs | ||
| Pairing.hs | ||
| Preferences.hs | ||
| Ssh.hs | ||
| WebDAV.hs | ||
| XMPP.hs | ||