From b1aaebf48bcc0183ccf4e591f89559ae714b95fa Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 21 Mar 2023 13:55:23 -0400 Subject: [PATCH] comment --- ...mment_2_0dbf6fcd15007ba66323ecf2b154ad2e._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Lost_git_repository._Recovery_from_S3_remote__63__/comment_2_0dbf6fcd15007ba66323ecf2b154ad2e._comment diff --git a/doc/forum/Lost_git_repository._Recovery_from_S3_remote__63__/comment_2_0dbf6fcd15007ba66323ecf2b154ad2e._comment b/doc/forum/Lost_git_repository._Recovery_from_S3_remote__63__/comment_2_0dbf6fcd15007ba66323ecf2b154ad2e._comment new file mode 100644 index 0000000000..9c14f9185b --- /dev/null +++ b/doc/forum/Lost_git_repository._Recovery_from_S3_remote__63__/comment_2_0dbf6fcd15007ba66323ecf2b154ad2e._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2023-03-21T17:54:02Z" + content=""" +@Lukey is probably right. The one exception would be if the +S3 remote was set up with encryption=pubkey. Then the files +stored in the bucket would be simply encrypted to your gpg public key, and +could be decrypted without needing any other information that you've lost. + +(The filenames would still not be able to be recovered.) +"""]]