diff options
| -rw-r--r-- | doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_2_26a695c892dd33b00fe8a2a36a0e284c._comment | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_2_26a695c892dd33b00fe8a2a36a0e284c._comment b/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_2_26a695c892dd33b00fe8a2a36a0e284c._comment new file mode 100644 index 000000000..aab5512c4 --- /dev/null +++ b/doc/bugs/GPG_issues_with_pubkey___40__Again__63____41__/comment_2_26a695c892dd33b00fe8a2a36a0e284c._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="71.80.94.56" + subject="comment 2" + date="2014-02-06T21:51:05Z" + content=""" +Seems to me that when gpg fails with \"no such user id\", the obvious reason is that your \"X\" is a gpg key ID that gpg does not know about. + +I cannot reproduce anything like this problem when using a directory special remote and encryption=pubkey. +"""]] |