]> dgit.raspbian.org Git - git-annex.git/commitdiff
comment
authorJoey Hess <joeyh@joeyh.name>
Wed, 5 Jan 2022 19:56:14 +0000 (15:56 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 5 Jan 2022 19:56:14 +0000 (15:56 -0400)
doc/forum/Windows_-_gpg_fails_with_shared_encryption/comment_1_708da81b0678576a240ce7a388806e07._comment [new file with mode: 0644]

diff --git a/doc/forum/Windows_-_gpg_fails_with_shared_encryption/comment_1_708da81b0678576a240ce7a388806e07._comment b/doc/forum/Windows_-_gpg_fails_with_shared_encryption/comment_1_708da81b0678576a240ce7a388806e07._comment
new file mode 100644 (file)
index 0000000..7e9d571
--- /dev/null
@@ -0,0 +1,27 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-01-05T19:44:24Z"
+ content="""
+The shared encryption key is what git-annex passes to gpg as
+"C:\\Users\\REDACTED\\AppData\\Local\\Temp\\gpg8159".
+
+From the other forum thread,
+[[Failing_to_get_files_from_rclone_special_remote]], 
+you had many special remotes that somehow existed with
+the same name.
+
+There's a big question mark over how you even got into that state.
+initremote does not let two special remotes with the same name be created
+in the same repository so normally it would be rather hard to accomplish
+once, let alone multiple times. Without understanding more, it's hard for
+me to guess what has happened.
+
+It also might be some problem with your gpg on windows. 
+googling for "gpg: decryption failed: Bad session key" seems to find that
+the problem is split between the wrong encryption key and some kind of gpg
+bugs.
+
+If you still have the data, would deleting that special remote and starting
+over with setting up a new one (with a different name!) be an option?
+"""]]