diff --git a/doc/bugs/Unable_to_setup_gcrypt_Remote_with_encryption__61__shared/comment_1_ada804190026c4f2bbe85101dfaa6cb2._comment b/doc/bugs/Unable_to_setup_gcrypt_Remote_with_encryption__61__shared/comment_1_ada804190026c4f2bbe85101dfaa6cb2._comment
new file mode 100644
index 0000000000..3443536eac
--- /dev/null
+++ b/doc/bugs/Unable_to_setup_gcrypt_Remote_with_encryption__61__shared/comment_1_ada804190026c4f2bbe85101dfaa6cb2._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="lukasstraub2@bbbb2ef261a0994edda5f5f55999dfac5998d4e5"
+ nickname="lukasstraub2"
+ avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b"
+ subject="Workaround"
+ date="2018-12-04T19:37:37Z"
+ content="""
+As a workaround, I can include a \"gnupg\" Directory in the Repo and point the GNUPGHOME environment Variable at it. Then I simply create a single Key there and add the gcrypt Repo with encryption=hybrid. Altough I have to add the following to the gpg.conf (in the gnupg Directory inside the Repo) to prevent gpg from writing to the directory afterwards:
+pinentry-mode loopback
+no-auto-check-trustdb
+no-random-seed-file
+no-permission-warning
+quiet
+
+"""]]