blob: 887f9f1fdd93fe0db8af593dd43f11de3fa414f9 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
### Please describe the problem.
git-annex assistant uses wrong key if multiple are available. If there is only one gpg available it works without issue.
### What steps will reproduce the problem?
I tried to creating a new key through cli or assistant UI. I also tried to select preexisting key but it always appears to choose the initial key. Log below is creating a new key through assistant UI.
### What version of git-annex are you using? On what operating system?
git-annex version: 5.20140709-gc75193e on linux amd64 & os x 10.9.4
### Please provide any additional information below.
[[!format sh """
# If you can, paste a complete transcript of the problem occurring here.
# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
[2014-07-12 23:22:57 PDT] main: starting assistant version 5.20140709-gc75193e
[2014-07-12 23:22:57 PDT] Cronner: You should enable consistency checking to protect your data.
(Recording state in git...)
(scanning...) [2014-07-12 23:22:57 PDT] Watcher: Performing startup scan
(started...) gpg: Signature made Wed Jul 9 19:09:28 2014 PDT using DSA key ID 89C809CB
gpg: Can't check signature: public key not found
(encryption setup) (hybrid cipher with gpg key A1FE7E9BECB5C7CA) gcrypt: Development version -- Repository format MAY CHANGE
gcrypt: Repository not found: ssh://admin@nappy.local/share/backups/annex/
gcrypt: Development version -- Repository format MAY CHANGE
gcrypt: Repository not found: ssh://admin@nappy.local/share/backups/annex/
gcrypt: Setting up new repository
gcrypt: Remote ID is :id:smTV2DKvbvPIi7ftJLey
gcrypt: Encrypting to: -R A1FE7E9BECB5C7CA
gcrypt: Requesting manifest signature
To gcrypt::ssh://admin@nappy.local/share/backups/annex/
* [new branch] git-annex -> git-annex
ok
[2014-07-12 23:23:42 PDT] main: Syncing with nappy.local__share_backups_annex
gcrypt: Development version -- Repository format MAY CHANGE
gcrypt: Decrypting manifest
gpg: anonymous recipient; trying secret key 6DF1BC5D ...
gpg: cannot open tty `/dev/tty': Device not configured
gcrypt: Failed to decrypt manifest!
gcrypt: Development version -- Repository format MAY CHANGE
gcrypt: Decrypting manifest
gpg: anonymous recipient; trying secret key 6DF1BC5D ...
gpg: cannot open tty `/dev/tty': Device not configured
gcrypt: Failed to decrypt manifest!
# End of transcript or log.
"""]]
[[!tag forwarded]]
[[!meta title="using git-remote-gcrypt with multiple keys causes unncessary password prompts for keys that did not encrypt the repository"]]
> [[fixed|done]]; upgrade git-remote-gcrypt and `git config gcrypt.publish-participants true`
> and after the next push to the repo, it'll stop guessing at keys, and use
> the right one. git-annex will do this by default for new gcrypt
> repositories. --[[Joey]]
|
