comment
authorJoey Hess <joeyh@joeyh.name>
Wed, 26 Feb 2020 19:06:38 +0000 (15:06 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 26 Feb 2020 19:06:38 +0000 (15:06 -0400)
doc/bugs/gcrypt_special_remote_not_working/comment_1_7eadb5e4cdebed6bffee5182b4bfe87b._comment [new file with mode: 0644]

diff --git a/doc/bugs/gcrypt_special_remote_not_working/comment_1_7eadb5e4cdebed6bffee5182b4bfe87b._comment b/doc/bugs/gcrypt_special_remote_not_working/comment_1_7eadb5e4cdebed6bffee5182b4bfe87b._comment
new file mode 100644 (file)
index 0000000..90c0d16
--- /dev/null
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2020-02-26T19:04:47Z"
+ content="""
+Almost certainly a reversion caused by the special
+remote config overhaul in version 7.20200202.7.
+
+This is really bad. The one good thing is it does not
+seem to affect other types of special remotes, including
+ones that also use encryption=hybrid. Only gcrypt.
+"""]]