diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2014-02-26 18:34:18 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2014-02-26 18:34:18 +0000 |
| commit | 306088480786cf90d8c52397c24f53d5ad962364 (patch) | |
| tree | f540b6eac90bf946ce563c3473ad16437b70470c | |
| parent | 1ba00a8eeac4e8549d455e45715438829bd89152 (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/problems_with_android_and_gpg/comment_3_47510400e8e45a71a1581aed99a157a1._comment | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/problems_with_android_and_gpg/comment_3_47510400e8e45a71a1581aed99a157a1._comment b/doc/bugs/problems_with_android_and_gpg/comment_3_47510400e8e45a71a1581aed99a157a1._comment new file mode 100644 index 000000000..2f663d943 --- /dev/null +++ b/doc/bugs/problems_with_android_and_gpg/comment_3_47510400e8e45a71a1581aed99a157a1._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.146" + subject="comment 3" + date="2014-02-26T18:34:18Z" + content=""" +AFAICS, the messages about locking are a red herring, since shared encryption is being used, the public and secret key rings are not used. + +This problem seems to be explained here: <http://crypto.stackexchange.com/questions/1468/how-does-gpg-verify-succesful-decryption> + +It seems there must be a problem with the symmetric key used for shared encryption. Either the repository somehow has the wrong key in it, or the key is not extracted from the repository correctly somehow, or it's not fed into gpg correctly somehow. +"""]] |