bugs/Debian and MacOSX cannot read eachother's S3 credentialsgit-annexhttp://git-annex.branchable.com/bugs/Debian_and_MacOSX_cannot_read_eachother__39__s_S3_credentials/git-annexikiwiki2017-02-13T19:35:51Zcomment 1http://git-annex.branchable.com/bugs/Debian_and_MacOSX_cannot_read_eachother__39__s_S3_credentials/comment_1_e307e5d0ec02ed76dc7c3f0894770539/joey2017-02-13T19:35:51Z2017-02-13T18:27:02Z
<p>The .git/annex/creds/uuid files for S3 special remotes are supposed to
contain the S3 access credentials, the same values you set
<code>AWS_ACCESS_KEY_ID</code> and <code>AWS_SECRET_ACCESS_KEY</code> to. Since it's just some
high-entropy credentials, perhaps that's why you thought it looked garbled?</p>
<p>I doubt that the error message about the cause of the gpg error is
right; that is a workaround for an old bug in git-annex 5.20140916. Unless
you used such an old version to set up the special remote, it's probably
not related to that problem at all.</p>
<p>The actual problem seems to be:</p>
<pre><code>gpg: packet(2) with unknown version 13
gpg: [don't know]: invalid packet (ctb=6b)
</code></pre>
<p>This probably points to an incompatability between the gpg versions.
The easiest fix is probably to upgrade Debian to gpg 2.</p>
<p>With embedcreds, the S3 creds are symmetrically encrypted/decrypted
using gpg --symmetric. This is a less common way to use gpg,
and it could be that there's an incompatability with how different
versions of gpg do it.</p>