From dfb45ac63dd01cfedbf423d7f0ac4b65d43e9ab8 Mon Sep 17 00:00:00 2001 From: andrew Date: Thu, 19 Jul 2018 18:23:32 +0000 Subject: [PATCH] --- ...rent_filename_encryption_method_than_shared.mdwn | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/doc/bugs/sharedpubkey_is_using_a_different_filename_encryption_method_than_shared.mdwn b/doc/bugs/sharedpubkey_is_using_a_different_filename_encryption_method_than_shared.mdwn index cedc270522..0e325704e6 100644 --- a/doc/bugs/sharedpubkey_is_using_a_different_filename_encryption_method_than_shared.mdwn +++ b/doc/bugs/sharedpubkey_is_using_a_different_filename_encryption_method_than_shared.mdwn @@ -61,17 +61,6 @@ I am looking into [decrypting files in special remotes without git-annex](https: You can see that I am able to generate correctly the special remote key used by `remote2` the `shared` remote, `0332a66cded87db8ec8427280c171133c958754f`. But using the same method for `remote1` the `sharedpubkey` remote does not yield a meaningful key `bb3b1f4b27164c2edc81da32c43c64e8a4be75d8` - -### Please provide any additional information below. - -[[!format sh """ -# If you can, paste a complete transcript of the problem occurring here. -# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log - - -# End of transcript or log. -"""]] - ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) - +Yes. —[andrew](https://git-annex.branchable.com/users/andrew/)